This repository was archived by the owner on Jun 20, 2024. It is now read-only.
Weave-net CNI can not work on containerd=1.6.4 #3942
Comments
|
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 |
|
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 containerd/containerd#6921 (comment) 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 #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. |
skitt
added a commit
to skitt/shipyard
that referenced
this issue
Jun 29, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; both binaries are now named explicitly with their version number (kind-0.12 and kind-0.14). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. Signed-off-by: Stephen Kitt <[email protected]>
skitt
added a commit
to skitt/shipyard
that referenced
this issue
Jun 30, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; both binaries are now named explicitly with their version number (kind-0.12 and kind-0.14). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. Signed-off-by: Stephen Kitt <[email protected]>
skitt
added a commit
to skitt/shipyard
that referenced
this issue
Jun 30, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; both binaries are now named explicitly with their version number (kind-0.12 and kind-0.14). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. Signed-off-by: Stephen Kitt <[email protected]>
skitt
added a commit
to skitt/shipyard
that referenced
this issue
Jun 30, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; both binaries are now named explicitly with their version number (kind-0.12 and kind-0.14). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. Signed-off-by: Stephen Kitt <[email protected]>
skitt
added a commit
to skitt/shipyard
that referenced
this issue
Jul 6, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; kind 0.12 is installed as "kind", kind 0.14 as "kind-0.14" (we need a "kind" binary because other parts of our CI expect it). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. This will break OVN on K8s 1.24 since the OVN deployment script drives kind directly. Signed-off-by: Stephen Kitt <[email protected]>
skitt
added a commit
to skitt/shipyard
that referenced
this issue
Jul 6, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; kind 0.12 is installed as "kind", kind 0.14 as "kind-0.14" (we need a "kind" binary because other parts of our CI expect it). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. This will break OVN on K8s 1.24 since the OVN deployment script drives kind directly. Signed-off-by: Stephen Kitt <[email protected]>
skitt
added a commit
to submariner-io/shipyard
that referenced
this issue
Jul 6, 2022
kind 0.13 and 0.14 add support for Kubernetes 1.24, but the non-1.24 Kubernetes images used with these versions currently embed containerd 1.6.4, which breaks Weave (see weaveworks/weave#3942 for details). To allow testing Kubernetes 1.24, install kind 0.14, while preserving kind 0.12; kind 0.12 is installed as "kind", kind 0.14 as "kind-0.14" (we need a "kind" binary because other parts of our CI expect it). When Kubernetes 1.24 is requested, deploy it with kind 0.14, otherwise rely on 0.12. See https://github.com/kubernetes-sigs/kind/releases/tag/v0.13.0 and https://github.com/kubernetes-sigs/kind/releases/tag/v0.14.0 for details. This will break OVN on K8s 1.24 since the OVN deployment script drives kind directly. Signed-off-by: Stephen Kitt <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Linux k8s-master 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux$ kubectl version
$ docker logs weave
$ kubectl logs -n kube-system weave
$ ip route
$ ip -4 -o addr
$ sudo iptables-save
The text was updated successfully, but these errors were encountered: