Helm 4.3.1 Released, Solidifying Server-Side Apply and OCI as Core Kubernetes Deployment Standards

Helm 4.3.1 was released on October 15, 2026, as a patch release on the Helm 4 line. This update builds upon the foundational changes introduced with Helm 4.0.0 in November 2025, which marked the first major version update for the Kubernetes package manager in six years. Key among these advancements is the deepened integration and stabilization of Server-Side Apply (SSA) as the default for new installations, and comprehensive support for OCI (Open Container Initiative) registries for chart distribution. This release also includes various bug fixes and performance enhancements, ensuring a more reliable and efficient user experience. This release is particularly significant for practitioners because it solidifies the architectural shifts introduced in Helm 4. The move to Server-Side Apply directly addresses long-standing challenges in managing Kubernetes resources, especially in GitOps environments where multiple tools might contend for control over the same resources. By making SSA the default, Helm 4.3.1 helps mitigate configuration drift and provides a more predictable deployment outcome. The enhanced OCI support streamlines chart distribution, allowing teams to leverage existing container registries for Helm charts, simplifying their supply chain and improving security through signed packages and chart verification. These developments align with the broader trend in cloud-native ecosystems towards more declarative, automated, and secure application management. The adoption of SSA by default in Helm reflects Kubernetes' own evolution, where SSA has been a standard since version 1.22. The emphasis on OCI registries for chart distribution mirrors the industry's push for standardized artifact management, moving beyond bespoke chart repositories. Furthermore, the impending end-of-life for Helm 3, with security patches concluding in February 2027, makes upgrading to Helm 4 an urgent and necessary step for maintaining secure and supported Kubernetes deployments. In practice, practitioners should prioritize migrating to Helm 4.3.1. While Helm 4 is designed to be largely backward compatible with Helm 3 charts and releases, it's crucial to test existing charts and CI/CD pipelines thoroughly. Special attention should be paid to potential silent breaking changes related to `--wait` flags, post-renderers, and CI/CD scripts. Teams should also begin leveraging the new capabilities, such as the WebAssembly-based plugin system for enhanced extensibility and `kstatus` integration for more robust deployment monitoring. Adopting these features will not only improve deployment reliability and security but also position teams to take full advantage of future Helm advancements.