Digital Developer Conference: Cloud Security 2021 -- Build the skills to secure your cloud and data Register free

IBM Developer Blog

Follow the latest happenings with IBM Developer and stay in the know.

What's next for the CNCF containerd project and its adopters

With the exciting announcement on containerd’s graduation in the CNCF, what exactly does it mean? Phil Estes, IBM Distinguished Engineer & CTO for Container and Linux OS Architecture Strategy, shares his thoughts in the video below.

It’s possible that you are already a consumer of containerd in your platform and/or container toolsuite and just weren’t aware of it! Maybe you already use Kubernetes, Docker, or one of these other adopters which already depend on the containerd project. Many of these adopters are already using containerd to manage the container lifecycle. This would include creating, starting, and deleting containers as well as pushing and pulling your images from a container registry, for example. The Docker engine has been using containerd to manage the container runtime lifecycle for over two years.

If you haven’t heard of containerd, but are interested in more details on the container runtime itself, the Getting Started documentation is a great place to start.

If you were already using containerd, you might ask what the CNCF graduated status means for you and others. From a purely technical perspective, not much changes. However, given the CNCF’s criteria for graduated projects, many see CNCF graduation as a “stamp of approval” on a project’s maturity, broad usage, and commitment to stability and security principles. With containerd’s growing popularity with cloud operators (IBM and Google both back and use the project) as well as developers, you can expect to see more collaboration and further advancements as containerd continues to mature in 2019 and beyond.

If you’re currently using the IBM Cloud Kubernetes Service (IKS) and are interested in how we use containerd, check out this blog post: “IBM Cloud Kubernetes Service Supports containerd.” If you have further questions on our migration to containerd as our Kubernetes runtime, we’d be happy to talk to you via our Slack channels or reach out to us on Twitter. (Get an invite to our Slack team by registering here and find us on the #general channel on our public IKS Slack team.)

Our team here at IBM has been significantly involved in the containerd open source project, with two upstream maintainers in both the core and CRI (the Kubernetes Container Runtime Interface) components of the codebase. We also make sure that containerd compiles and runs properly on our z Systems and POWER platforms as well, since these platforms also run cloud native workloads via both Docker and Kubernetes.

We’re excited to see the direction that containerd will take from here. Congratulations to all the participants who helped make containerd a successfully graduated project!