containerd 2.3 is coming right around the corner, and with it we’ve made some changes to how we produce our releases. I won’t bury the lede here, starting with containerd 2.3, we now have:
- Annual LTS releases with a two-year support window (starting with 2.3)
- New releases every four months, aligned with Kubernetes
- Regular releases now get eight months of support
- Improved upgrade safety by limiting breaking changes to the first release after an LTS
- Supported upgrades from one LTS version to the next
These are some big changes! I hope you’ll see that they are also useful:
- More frequent releases get features and enhancements out the door faster
- It’s easy to upgrade your Kubernetes cluster and containerd at the same time
- It accelerates Kubernetes development by ensuring containerd is ready for new KEPs
- You can be confident that upgrading into the next LTS release is safe, and then take advantage of its stability
- If you prefer LTS releases, they are now predictable
Some things also haven’t changed:
- containerd remains committed to supporting lots of use-cases. While the release cycle is synchronized with Kubernetes, usage with Docker (Moby) and other clients is just as important as before
- containerd is a welcoming community and encourages you to get involved
We made these decisions at the end of February when I organized a maintainer summit for us at Google Seattle. This was all outlined in my proposal, but it really took all of us to come together, discuss, and reach consensus. I’m thrilled that our community is able to work together so well and make meaningful improvements!
If you’d like to be involved in containerd, please join us in the CNCF Slack #containerd and #containerd-dev channels, join our community meetings, open issues, discussions, or PRs on GitHub, and get involved with reviewing some PRs yourself!
Comments via 🦋
Join the conversation