I'm in the process of transitioning from RKE v1 clusters to either K3S or another method for deployment. Given that the Kubernetes project has announced that v1.35 will be the last version to support containerd 1.x, I'm particularly concerned about Ubuntu 24, Debian 12, and 13 coming with containerd versions 1.7.x or 1.6.x. Does anyone have suggestions on how to avoid relying on the distro's packaging of containerd, especially with this compatibility issue looming? I haven't yet explored the idea of repackaging it myself, though I think the binary deployment should be fairly straightforward. I'm curious to see how others are planning to address this change.
2 Answers
K3S might be a solid option since it bundles its own version of containerd, so you won’t have to deal with issues from the host OS version. That should streamline things for you!
Have you looked into using Talos or RKE2? They can handle the containerd requirement pretty well and might simplify your setup.
+1 for Talos! It's been working smoothly for my small clusters.
Oh?! I didn’t realize that at all. Well, that makes things a lot easier then. Thank you!