Menu

The countdown is on: Kubernetes disables cgroup v1 – a migration checklist for 2026
📰

The countdown is on: Kubernetes disables cgroup v1 – a migration checklist for 2026

DEV Community: kubernetes·saaro·15 days ago
#E83XqiDM
#devtokubernetes#devto#dev#cgroup#kubernetes
Reading 0:00
15s threshold

The countdown is on: Kubernetes shuts down cgroup v1 – a migration checklist for 2026

Since Kubernetes 1.37 in August 2026 at the latest, the message is unmistakable: the kubelet no longer starts on a cgroup v1 node – unless an administrator explicitly sets the temporary failCgroupV1: false . What many teams saw as a side note in the release notes is now becoming operational reality. Kubernetes 1.34 reached the end of its support cycle on October 27, 2026, and with every upgrade to 1.35 or newer, the cgroup v2 migration is on the table. Those who do not act now risk nodes that simply fail to come up after the next upgrade.

Why cgroup v2?

cgroups (Control Groups) are the Linux kernel mechanism that Kubernetes uses to enforce CPU and memory limits for containers. cgroup v1 organised this control over several separate hierarchies – one per resource controller.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.