Kubernetes drops cgroup v1: kubelet won't start on legacy nodes
Starting with Kubernetes v1.35, kubelet refuses to start on nodes running cgroup v1 by default. Developers recommend migrating every Linux node to cgroup v2 before upgrading, citing its unified hierarchy, memory QoS and rootless support.
- Kubernetes v1.35 kubelet won't start on cgroup v1 nodes by default
- cgroup v2 offers a unified hierarchy, memory QoS and container-aware OOM
- Node swap in v1.34 boosts cluster density up to 3x on NVMe SSDs
- Kubernetes on Edge Day runs at KubeCon on November 9-12 in Salt Lake City
Read next
Software