Kubernetes cleans house, bins legacy kube-dns, IPVS, and cgroup v1
- ID
- 18410
- Status
- summarized
- Published
- 27 Aug 2026, 4:54 AM
- Fetched
- 27 Aug 2026, 7:08 AM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/devops/2026/08/26/kubernetes-cleans-house-bins-legacy-kube-dns-ipvs-and-cgroup-v1/5292717
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 7.0
- Created
- 27 Aug 2026, 7:10 AM
- Tags
- Audience
- developersvibe_coders
What happened
Kubernetes v1.37 (nicknamed Garhwal) ships 67 changes: 16 features reaching stable GA, 23 beta, 27 alpha, and 1 deprecation. The release removes legacy kube-dns, IPVS, and cgroup v1 support, and finally promotes the Metrics API to general availability after nine years stuck in beta. CNCF reports 82% of container users now run Kubernetes in production, and 66% of organizations hosting generative AI models use Kubernetes for inference workloads.
Why it matters
If you operate Kubernetes clusters, v1.37's removal of cgroup v1, kube-dns, and IPVS means you must verify your nodes run cgroup v2 and your DNS routing doesn't depend on the legacy kube-dns path before upgrading. The Metrics API GA after nine years of beta means any tooling still referencing v1beta1 Metrics API endpoints should be updated to the stable version to avoid future breakage.
Discussion angle
With 66% of genAI inference workloads now on Kubernetes, the cgroup v1 deprecation is especially relevant for teams running GPU-bound model serving — cgroup v2 changes how resource limits and device access work, which can affect GPU scheduling and memory isolation on older node images.