Insights into Kubernetes v1.35 Features and Changes
The upcoming Kubernetes v1.35 release signifies a pivotal moment focused on both deprecation of legacy support and the introduction of enhancements aimed at stabilizing and streamlining functionality within the Kubernetes ecosystem. As organizations continue to embrace Kubernetes for container orchestration, understanding these changes is crucial in maintaining optimal performance and ensuring system reliability.
What Matters in Kubernetes v1.35
With Kubernetes v1.35, the overarching theme reflects a commitment to modernization and efficiency. The plan to deprecate certain features while graduating others to general availability is no mere housekeeping. These changes not only aim to alleviate technical debt but also signal a shift towards best practices that align with developers’ needs and the evolving tech landscape.
Key Deprecations in v1.35
One of the most significant deprecations is the removal of cgroup v1 support. Kubernetes has supported cgroup v2 since v1.25, implementing a more stable and unified control mechanism that improves resource isolation. As many administrators may still operate on older Linux distributions lacking cgroup v2 support, this move pushes organizations to adopt more modern systems. Failure to migrate means that the kubelet won't start, creating potential deployment issues for those unprepared for change. This is more than just an update; it’s a call to action for admins to modernize their infrastructure.
Another noteworthy deprecation involves the kube-proxy's ipvs mode. Initially designed to enhance service load balancing, it has recently become a burden due to the growing complexity of maintaining parity among different proxy modes. The move away from ipvs simplifies the kube-proxy codebase, allowing developers to focus on more robust and powerful components, particularly the recommended nftables mode. The instinct might be to view this merely as a technical tidy-up, but it actually represents a broader shift in Kubernetes' philosophy towards making life easier for developers managing service traffic.
Lastly, support for containerd v1.x will be removed, making v1.35 the last release where it’s still available. Organizations still running this version must pivot to containerd v2.0 or newer before the next upgrade, and the kubelet_cri_losing_support metric will be critical to monitor. This serves as a reminder that keeping up with proactive infrastructure maintenance is as important as the Kubernetes versions themselves.
Enhancements Driving Kubernetes Forward
The enhancements slated for v1.35 are designed to improve usability, security, and operational efficiency. The introduction of **node declared features** will allow nodes to explicitly state what Kubernetes features they can support. This will reduce complications tied to version skews during upgrades, ultimately resulting in more reliable scheduling and deployment. It's an elegant move to essentially say, "let’s clarify our capabilities"—a much-needed tweak given the frequent updates within the ecosystem.
Graduating the **in-place update of Pod resources** to General Availability is another milestone change. This capability allows administrators to modify CPU and memory requests without needing to restart Pods—reducing downtime and enhancing workload operations for both stateless and stateful applications. The evolution of this feature from alpha to beta and now to an official release underscores Kubernetes' commitment to improving user experience.
The **pod certificates** enhancement is particularly noteworthy for those navigating microservices architectures. Instead of relying on external projects for cryptographic identities and certificate rotations, this update allows Kubernetes to manage certificate provisioning natively, simplifying service authentication in zero-trust environments. By streamlining security for pod-to-pod communication, this enhancement sets the stage for more secure deployments without the operational overhead traditionally associated with certificate management.
What This Means for Developers and Operations Teams
For developers, these changes herald a more efficient, less burdensome approach to managing Kubernetes clusters. The deprecations may be challenging in the short term, but they pave the way for a more streamlined environment that can better support modern applications. The enhancements particularly stand out as improvements not just for Kubernetes users but also for enabling developers to innovate without being constrained by legacy support issues.
As operations teams prepare for the new version, the focus should be on assessing current deployments to ensure compatibility with v1.35. Managing a proactive upgrade strategy will be key in avoiding disruptions. Continuous monitoring of metrics and keeping abreast of Kubernetes developments will become increasingly vital as the platform evolves.
Looking Ahead to Kubernetes v1.35
The expected release of Kubernetes v1.35 on December 17, 2025, serves as an important reminder of the project's commitment to refining its toolset while phasing out deprecated features. For organizations, this isn't just about updating software; it's a holistic challenge that encompasses upgrading infrastructure, revisiting deployment strategies, and maintaining security compliance. The changes anticipate a landscape where Kubernetes can scale more effectively and function more securely, which is the ultimate goal for any cloud-native operation.
As we approach the official rollout, keeping tuned to the release notes and community discussions will ensure you're not just prepared for the transition but also informed of how to leverage the capabilities that Kubernetes v1.35 will offer. Engaging with the Kubernetes community will provide further insights into how these changes can be maximized across various environments.
