-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
更新默认Cilium版本以修复一个已知Bug #1779
更新默认Cilium版本以修复一个已知Bug #1779
Conversation
As a known Cilium bug with version 1.11.6 from: cilium/cilium#20437 The only solution is updating the version to 1.11.7: cilium/cilium#20437 (comment) I could not boot up the kubernetes cluster with coredns network error: ``` │ [ERROR] plugin/errors: 2 2172798194240639882.4750332868417339179. HINFO: read udp 10.233.128.89:52976->8.8.8.8:53: i/o timeout │ [ERROR] plugin/errors: 2 2172798194240639882.4750332868417339179. HINFO: read udp 10.233.128.89:33783->8.8.8.8:53: i/o timeout │ [ERROR] plugin/errors: 2 2172798194240639882.4750332868417339179. HINFO: read udp 10.233.128.89:35504->8.8.8.8:53: i/o timeout │ [INFO] SIGTERM: Shutting down servers then terminating │ [INFO] plugin/health: Going into lameduck mode for 5s ``` Cilium error: ``` cilium-health-ep 34m31s ago 57s ago 39 Get "http://10.233.128.42:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers) ```
@littleplus Thanks for this contribution! The helm chat of cilium also needs to be updated. |
#1794 I have submitted another pr to update cilium's chart. |
/lgtm |
LGTM label has been added. Git tree hash: a6002552711e79fb891d44e3d725157ff2b21903
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: littleplus, pixiake The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@all-contributors please add @littleplus for code |
As a known Cilium bug with version 1.11.6 from: cilium/cilium#20437
The only solution is updating the version to 1.11.7: cilium/cilium#20437 (comment)
I could not boot up the kubernetes cluster with coredns network error:
Kubekey Config:
CoreDNS error:
Cilium error:
What type of PR is this?
/kind bug
What this PR does / why we need it:
Update default cilium version from v1.11.6 to v1.11.7
Which issue(s) this PR fixes:
Fixes cilium/cilium#20437
Does this PR introduced a user-facing change?