Open fuzhibo opened 2 years ago
Up for this Issue.
For more details, see:
I'm not sure if it's weave's fault or containerd's fault; if it's weave's I guess they'll want to fix it; if it's containerd's they'll want to advocate and explain why 😅
Can confirm as well on kubernetes v1.24.1/weave 2.8.1 where downgrading to containerd.io=1.5.11-1
solved the issue too.
and I am sure until they find who's fault was it, people will forget weave altogether on Kubernetes, my guess after seeing that weave was last updated about an year ago
If there is someone who has the chops and wants to see Weave net maintained, send your PRs @ me and I will help you to try and get them merged.
My understanding from https://github.com/containerd/containerd/issues/6921#issuecomment-1146680225 is that this all works again, thanks to a change from upstream which has resolved the backwards-incompatible changes in CNI.
Which means of course, people can install weave net again (and they might be in danger with no maintainers actively pushing out releases.)
(Edit: the discussion in https://github.com/weaveworks/weave/pull/3939 is a good place to start if you haven't seen it yet.)
Meanwhile, I can confirm that weave net works as-is on containerd 1.6.6, with Kubernetes 1.24, 1.23 and 1.22.
What you expected to happen?
Using Weave-net CNI for kubernetes=v1.20.1
What happened?
Found weave-net CNI can not work on kubernetes=v1.20.1 and containerd.io=1.6.4, the veth of containers can not be created.
How to reproduce it?
Upgrade containerd.io to 1.6.4
Anything else we need to know?
When I downgrades containerd.io=1.5.11,everything works.
Versions:
$ uname -a
$ kubectl version
$ docker logs weave
$ kubectl logs -n kube-system weave
$ ip route $ ip -4 -o addr $ sudo iptables-save