Skip to content
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

k8s 1.29 使用 calicao v3.27.3 calico-kube-controllers 无法成功运行 #18764

Open
fs2016l opened this issue Apr 27, 2024 · 3 comments
Open
Labels
l/zh-CN Issues in or relating to Chinese

Comments

@fs2016l
Copy link

fs2016l commented Apr 27, 2024

Type Reason Age From Message


Normal Scheduled 114m default-scheduler Successfully assigned kube-system/calico-kube-controllers-7b84757b95-576fg to y3
Warning FailedCreatePodSandBox 114m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "3d6733531c3caf74141893557e9d697f5ba909a3a08874087ed6892142153048" network for pod "calico-kube-controllers-7b84757b95-576fg": networkPlugin cni failed to set up pod "calico-kube-controllers-7b84757b95-576fg_kube-system" network: plugin type="calico" failed (add): error creating calico client: stat /etc/cni/net.d/calico-kubeconfig: no such file or directory
Warning FailedCreatePodSandBox 114m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "80e85e2e540352d3d3f488bed5e59b6639294764e97573dfc98897ce7b5dd4a1" network for pod "calico-kube-controllers-7b84757b95-576fg": networkPlugin cni failed to set up pod "calico-kube-controllers-7b84757b95-576fg_kube-system" network: plugin type="calico" failed (add): error creating calico client: stat /etc/cni/net.d/calico-kubeconfig: no such file or directory
Normal SandboxChanged 114m (x3 over 114m) kubelet Pod sandbox changed, it will be killed and re-created.
Warning Unhealthy 113m (x7 over 114m) kubelet Readiness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Normal Pulled 113m (x2 over 114m) kubelet Container image "calico/kube-controllers:v3.27.3" already present on machine
Normal Started 113m (x2 over 114m) kubelet Started container calico-kube-controllers
Normal Created 113m (x2 over 114m) kubelet Created container calico-kube-controllers
Warning Unhealthy 113m (x2 over 114m) kubelet Readiness probe failed: initialized to false
Warning Unhealthy 99m (x31 over 114m) kubelet Liveness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Warning BackOff 89m (x82 over 110m) kubelet Back-off restarting failed container calico-kube-controllers in pod calico-kube-controllers-7b84757b95-576fg_kube-system(2c51d34d-8381-4968-8240-6ba7a469dbdf)
Normal SandboxChanged 85m (x2 over 85m) kubelet Pod sandbox changed, it will be killed and re-created.
Warning Unhealthy 85m kubelet Readiness probe failed: initialized to false
Normal Pulled 84m (x2 over 85m) kubelet Container image "calico/kube-controllers:v3.27.3" already present on machine
Normal Created 84m (x2 over 85m) kubelet Created container calico-kube-controllers
Normal Started 84m (x2 over 85m) kubelet Started container calico-kube-controllers
Warning Unhealthy 83m (x9 over 85m) kubelet Readiness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Warning Unhealthy 70m (x26 over 85m) kubelet Liveness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Warning BackOff 50m (x123 over 84m) kubelet Back-off restarting failed container calico-kube-controllers in pod calico-kube-controllers-7b84757b95-576fg_kube-system(2c51d34d-8381-4968-8240-6ba7a469dbdf)
Normal SandboxChanged 46m (x2 over 47m) kubelet Pod sandbox changed, it will be killed and re-created.
Normal Pulled 46m kubelet Container image "calico/kube-controllers:v3.27.3" already present on machine
Normal Created 46m kubelet Created container calico-kube-controllers
Normal Started 46m kubelet Started container calico-kube-controllers
Warning Unhealthy 46m kubelet Readiness probe failed: initialized to false
Normal SandboxChanged 44m (x2 over 46m) kubelet Pod sandbox changed, it will be killed and re-created.
Normal Pulled 43m (x2 over 44m) kubelet Container image "calico/kube-controllers:v3.27.3" already present on machine
Normal Created 43m (x2 over 44m) kubelet Created container calico-kube-controllers
Warning Unhealthy 43m (x6 over 44m) kubelet Liveness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Normal Killing 43m kubelet Container calico-kube-controllers failed liveness probe, will be restarted
Warning Unhealthy 43m kubelet Readiness probe failed: OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown
Normal Started 43m (x2 over 44m) kubelet Started container calico-kube-controllers
Warning Unhealthy 43m (x2 over 44m) kubelet Readiness probe failed: initialized to false
Warning Unhealthy 16m (x60 over 44m) kubelet Readiness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Warning BackOff 58s (x157 over 42m) kubelet Back-off restarting failed container calico-kube-controllers in pod calico-kube-controllers-7b84757b95-576fg_kube-system(2c51d34d-8381-4968-8240-6ba7a469dbdf)

@fs2016l fs2016l added the l/zh-CN Issues in or relating to Chinese label Apr 27, 2024
@fs2016l
Copy link
Author

fs2016l commented Apr 27, 2024

Warning FailedCreatePodSandBox 114m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "3d6733531c3caf74141893557e9d697f5ba909a3a08874087ed6892142153048" network for pod "calico-kube-controllers-7b84757b95-576fg": networkPlugin cni failed to set up pod "calico-kube-controllers-7b84757b95-576fg_kube-system" network: plugin type="calico" failed (add): error creating calico client: stat /etc/cni/net.d/calico-kubeconfig: no such file or directory
Warning FailedCreatePodSandBox 114m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "80e85e2e540352d3d3f488bed5e59b6639294764e97573dfc98897ce7b5dd4a1" network for pod "calico-kube-controllers-7b84757b95-576fg": networkPlugin cni failed to set up pod "calico-kube-controllers-7b84757b95-576fg_kube-system" network: plugin type="calico" failed (add): error creating calico client: stat /etc/cni/net.d/calico-kubeconfig: no such file or directory

Warning Unhealthy 83m (x9 over 85m) kubelet Readiness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host
Warning Unhealthy 70m (x26 over 85m) kubelet Liveness probe failed: Error initializing datastore: Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.96.0.1:443: connect: no route to host

@fs2016l
Copy link
Author

fs2016l commented Apr 27, 2024

我已经放开了防火墙的443端口,但是这没有效果
当我关闭整个防火墙时,他才能成功运行

@fs2016l
Copy link
Author

fs2016l commented Apr 27, 2024

这个问题该如何解决呢

@fs2016l fs2016l changed the title k8s 1.29 使用 calicao v3.27.3 alico-kube-controllers 无法成功运行 k8s 1.29 使用 calicao v3.27.3 calico-kube-controllers 无法成功运行 Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
l/zh-CN Issues in or relating to Chinese
Projects
None yet
Development

No branches or pull requests

1 participant