Kubernetes v1.35 Preview: Key Deprecations and Enhancements
The upcoming Kubernetes v1.35 release introduces significant changes aimed at improving project health and operational stability. A major update is the complete removal of cgroup v1 support, requiring administrators to migrate nodes to Linux distributions supporting cgroup v2 to prevent kubelet failures. Additionally, the ipvs mode in kube-proxy is being deprecated to reduce technical debt and streamline the codebase, with nftables recommended as the preferred alternative for Linux nodes. The release also marks the end of support for containerd v1.x versions; users must upgrade to containerd 2.0 or later before moving to subsequent Kubernetes versions. On the enhancement front, the release features 'Node declared features,' designed to address version skew issues during cluster upgrades by ensuring Pods are not scheduled on nodes lacking necessary capabilities. These updates reflect the Kubernetes community's ongoing effort to modernize infrastructure components, enforce better resource isolation, and simplify maintenance. Administrators are urged to review these deprecations and plan migrations accordingly to ensure seamless cluster operations post-upgrade.
Wire timeline
Kubernetes v1.35 Preview: Key Deprecations and Enhancements
The upcoming Kubernetes v1.35 release introduces significant changes aimed at improving project health and operational stability. A major update is the complete removal of cgroup v1 support, requiring administrators to migrate nodes to Linux distributions supporting cgroup v2 to prevent kubelet failures. Additionally, the ipvs mode in kube-proxy is being deprecated to reduce technical debt and streamline the codebase, with nftables recommended as the preferred alternative for Linux nodes. The release also marks the end of support for containerd v1.x versions; users must upgrade to containerd 2.0 or later before moving to subsequent Kubernetes versions. On the enhancement front, the release features 'Node declared features,' designed to address version skew issues during cluster upgrades by ensuring Pods are not scheduled on nodes lacking necessary capabilities. These updates reflect the Kubernetes community's ongoing effort to modernize infrastructure components, enforce better resource isolation, and simplify maintenance. Administrators are urged to review these deprecations and plan migrations accordingly to ensure seamless cluster operations post-upgrade.
Kubernetes Blog