Open beacon-hash opened 2 years ago
For kubernetes 1.23.x I face some similar issue with weave v2.8.1.
Please give a try as https://github.com/weaveworks/weave/pull/3939#issuecomment-1099812129, with a patched version which working for newly provisioned cluster (work for both upgrade a new cluster from kubernetes 1.21.x -> 1.22.x -> 1.23.x, or a direct new install from 1.23.x).
What you expected to happen?
Expected weave-net pods to be up and running on all worker nodes.
What happened?
The pods are giving CrashLoopBackOff error.
How to reproduce it?
I don't know how to reproduce the error.
Anything else we need to know?
I'm just trying to install Kubernetes manually service by service and everything worked fine as expected except weave-net. I'm using L4 load balancer in front of two instances of kube-apiservers and every service on worker nodes are pointing to the load balancer.
Versions:
Logs: