Kubernetes has officially transitioned cgroup v1 to maintenance mode and initiated its deprecation, with v2 becoming the standard for resource management. The migration requires transitioning Linux nodes to cgroup v2, as kubelet versions 1.35 and later will fail to start on v1-based systems by default. This change provides a unified hierarchy and improved resource isolation mechanisms for modern container workloads.
Key points
Kubernetes v1.35 introduces a default 'failCgroupV1: true' setting, preventing kubelet startup on nodes using the legacy cgroup v1 interface.
cgroup v2 offers a unified hierarchy and more consistent resource management compared to the fragmented v1 structure.
The kubeadm 'SystemVerification' preflight check now enforces cgroup v2 compliance for new clusters and upgrades starting at version 1.35.
Migration requires kernel-level configuration changes on Linux hosts, as v1 support is slated for total removal per the Kubernetes deprecation policy.