← Thursday, October 8, 2026Cloud & infraGuide

Kubernetes is moving away from cgroup v1 toward v2

kubernetes.io 11 min read Editor score 7/10

Kubernetes moved cgroup v1 management into maintenance in v1.31, and v1.35 defaults to refusing startup on cgroup v1 nodes unless overridden. Teams should plan node migration before upgrading.

What
Kubernetes is deprecating cgroup v1 and moving toward cgroup v2 for Linux node resource management.
How
In Kubernetes v1.35, failCgroupV1 defaults to true, so the kubelet does not start on a cgroup v1 node unless overridden.
Why it matters
Engineers should migrate Linux nodes before upgrading; cgroup v2 also enables the memory controller features used by Memory QoS.

Discussion

Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.

Your note

Private to you. Stored in this browser, and synced to your account when you are signed in.