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

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. Now, we've (almost) arrived at the end of that headache. Automated cgroup driver detection In v1.28.0, the SIG Node community introduced the feature gate KubeletCgroupDriverFromCRI , which instructs the kubelet to ask the CRI implementation which cgroup driver to use. You can read more here . After many releases of waiting for each CRI implementation to have major versions released and packaged in major operating systems, this feature has gone GA as of Kubernetes 1.34.0. In addition to setting the feature gate, a cluster admin needs