Menu

1 / 2

Kubernetes 1.35: kubelet will not start on cgroup v1

DEV Community: kubernetes·R (RYUSLOG DEV)·about 3 hours ago
#z1PrJJMh
#devtokubernetes#devto#dev#node#kubelet
Long article (1506 words) — no AI summary yet.
Reading 0:00
15s threshold

Introduction & Quick Summary

Symptom. After upgrading a cluster's nodes to Kubernetes 1.35, new nodes never become Ready . The kubelet on the node exits almost immediately:

$ systemctl status kubelet Active: failed (Result: exit-code)

$ journalctl -u kubelet -n 20 --no-pager ... kubelet: cgroup v1 is no longer supported; failing to start

Enter fullscreen mode

Exit fullscreen mode

$ kubectl get nodes NAME STATUS ROLES AGE VERSION worker-3 NotReady <none> 4m v1.34.9

Enter fullscreen mode

Exit fullscreen mode

The node object is registered by an older kubelet or not at all, pods stay Pending , and kubectl describe node worker-3 shows Ready False with KubeletNotReady .

Cause. Kubernetes 1.35 removed cgroup v1 support. A node booting on cgroup v1 with a 1.35 kubelet does not join, and the failure is at the host, not in any Kubernetes object.…

Continue reading — create a free account

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