Historically, configuring the correct cgroup driver has been a pain point for users running new Kubernetes clusters. On Linux systems, there are two different cgroup drivers: cgroupfs and systemd. In the past, both the kubelet and CRI implementation (like CRI-O or containerd) needed to be configured to use the same cgroup driver, or else the kubelet would misbehave without any explicit error message. This was a source of headaches for many cluster admins.

Kubernetes is an open-source container orchestration platform for automating the deployment, scaling, and management of containerized applications. With Kubernetes, developers can deploy applications across clusters of machines, ensuring high availability, scalability, and resilience. Developers can learn about Kubernetes' architecture, core concepts, and deployment strategies, and gain hands-on experience with managing containerized workloads using Kubernetes.

Kubernetes

Kubernetes v1.34 introduces GA support for automatic cgroup driver detection, eliminating the need for manual configuration between kubelet and CRI implementations. The feature allows kubelet to automatically query the CRI for the correct cgroup driver, solving a common cluster administration pain point. Additionally, Kubernetes announces deprecation of containerd v1.y support, with final support ending in v1.35 and complete removal in v1.36.0.

Kubernetes v1.34: Autoconfiguration for Node Cgroup Driver Goes GA

Announcement: Kubernetes is deprecating containerd v1.y support