-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
docker.io/flannel/flannel-cni-plugin:v1.5.1-flannel1 can not running #2031
Comments
So the only node that it's failing is the one with arm64? I'll check if the container for arm64 was rightly created. |
Thank you for your reply.
|
Which is the output for |
|
I face a very similar looking problem: the Flannel It fails on the
It does not give any output:
as I understand
This comes while upgrading Kubernetes from Looking into CHANGELOG-1.31 I am lost at what could be releated. I somehow guess it may be related to the use of Downward API for two |
I reversed my Kubernetes version from ... so I think there is clearly a problem coming from the changes with Kubernetes |
Hi Can you show the kernel version that you're using and the kernel logs? |
the system is
to switch the K8s version I toggle the (this is Flatcars way of "blending in" software utilizing systemd-sysext with their sysext-bakery For kernel logs I can't do that right now, as I would need to take down a node to get a clean one and they are all busy. Note that the kernel version and OS version does not change here, I really only toggle the K8s binaries and reboot to have it all start properly after "blending". |
meanwhile there has been a small kernel + OS update, but this problem here is unchanged. I had a chance to produce fresh dmesg and journalctl logs, please find them attached:
this far I don't see how to bring my cluster to Kubernetes 1.31.0 given that Flannel does not come up... appreciate any idea how to approach this. |
@x3nb63 I don't notice anything in
which then prevents the flannel pod from starting:
That also explains these messages:
because the flannel pod is the one that should write so it looks like the upgrade somehow breaks the cluster configuration. Do you have the possibility to install a new cluster from scratch using version |
thanks for explaining these connections! kube-apiserver pods are healthy, however I am now spotting all except one control-plane node still use image Certainly not Flannels fault. |
all right, I follow https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-reconfigure/ to get this sorted essentially per control-plane node
so far Flannel is still not starting but I progressed (I'll update this post once I know what to do while not risking all control-plane nodes) |
after previous step its stuck on a different thing as the "spec.ClusterIP unknown" errors are totally gone. As I see it, kubelet is now at 1.31.1 properly and so are all kube-system Pods on said node. Except for kube-proxy, which also relies on Flannel, I suppose. The flannel Pod now appears to not come up because of Flannel Pod is still stuck in init on
What I dont get is why Flannel Pod would want Which makes me think: May it be a problem with DualStack? This is what |
Expected Behavior
k8s pod kube-flannel-ds-vjhqf is ready; docker.io/flannel/flannel-cni-plugin:v1.5.1-flannel1 is functioning properly
Current Behavior
k8s pod kube-flannel-ds-vjhqf is always at state: Init:RunContainerError
pod kube-flannel-ds-vjhqf failed at
Possible Solution
Steps to Reproduce (for bugs)
Context
node can never be ready in k8s cluster
I'm using an arm64 machine as node to join a x86 cluster, does it matter?
Your Environment
The text was updated successfully, but these errors were encountered: