“Containerd has become the industry-standard container runtime focused on simplicity, robustness and portability.” said Carmine Rimi, product manager for Kubernetes at Canonical. “Enabling Kubernetes to drive containerd directly reduces the number of moving parts, reduces latency in pod startup times, and improves CPU and memory usage on every node in the cluster.”
The traditional Docker runtime will also continue to be supported in Canonical’s Kubernetes offerings. Clusters will preserve their choice of runtime during upgrades.
“After being accepted into CNCF nearly two years ago, containerd continues to see significant momentum – showcasing the demand for foundational container technologies,” said Chris Aniszczyk, CTO of the Cloud Native Computing Foundation.
Canonical provides multi-cloud Kubernetes operations, compatibility and portability, supporting customers on Amazon EKS, Azure AKS, and Google GKE with Ubuntu worker nodes, and Charmed Kubernetes and MicroK8s for on-premise Kubernetes.