-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: bump Containerd to 1.6.24 #922
Conversation
Why can't we bump to 1.7.x? |
Ah, we can! Just checked https://github.com/containerd/containerd/blob/main/RELEASES.md#kubernetes-support |
8e9e4c2
to
881823e
Compare
I wouldn't be comfortable merging a 1.7.x bump before testing some images built with KIB in Konvoy. |
881823e
to
7a0eddb
Compare
@faiq when did the podman build get broken? Will we need to backport for DKP 2.6? If so, please pull those commits out into a separate PR. |
To me the issue with podman seems to be rooted with using the binary with the embedded image. I'm not sure when this happened, but to work around it in the tests we are now pulling the image instead. For users that wish to you use podman as a container engine, it seems to me that they should not use the binary with the embeded image and opt to pull it instead. |
Based on this conversation we actually cannot upgrade containerd at this time. The containerd version is constrained by our Flatcar LTS version; see the previous PR for K8s 1.26 and Flatcar LTS release notes. |
@bcm820 do you mean here that you can't upgrade Flatcar, or are you saying we shouldn't upgrade Containerd at all? |
As discussed in the thread, I was confused about the dependency on containerd. Please disregard :) |
ba7e851
to
5b3f1ae
Compare
What problem does this PR solve?:
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: