NEW YORK — What happened: The Kubernetes release team has rolled out version 1.35, marking another major milestone for cloud-native container orchestration. This update prioritizes cluster hardening, cleaner API deprecations, and enhanced storage management primitives.
Why it matters: Managing stateful workloads and persistent storage in Kubernetes has historically been one of the most complex operational challenges for platform engineering teams. Version 1.35 introduces architectural changes aimed at simplifying these workflows.
Deep dive: Kubernetes 1.35 officially graduates dynamic volume resizing to general availability, allowing administrators to expand persistent storage volumes without restarting workloads or unmounting file systems. The control plane also introduces stricter default security policies for ephemeral storage, preventing rogue pods from consuming host node resources through unconstrained temporary file generation.
Report check: Claims vs what is verified vs still rumor. Release documentation confirms the stabilization of key storage APIs. Claims that Kubernetes 1.35 entirely removes the need for dedicated storage administration tools are unverified; specialized backup and disaster recovery solutions are still required for production environments.
Open questions: How will cloud providers adapt their managed Kubernetes control planes to support the newly deprecated API versions removed in this release?