Helm 3 Approaches End-of-Life: Final Feature Release and Extended Security Support Announced

The Helm maintainers have announced the impending end-of-life for Helm 3. A final, limited feature release for Helm 3 is scheduled for September 9th, 2026. This release will primarily focus on Kubernetes client library updates to ensure compatibility with newer Kubernetes versions. Following this, security patches for Helm 3 will be provided until February 10th, 2027. After this date, Helm 3 will no longer receive any updates, including security patches or further Kubernetes client library updates. This announcement is highly significant for any organization or individual still utilizing Helm 3 for their Kubernetes deployments. The cessation of security patches and Kubernetes client library updates means that Helm 3 installations will become increasingly vulnerable to security exploits and may encounter compatibility issues with newer Kubernetes clusters. For practitioners, this translates to a growing operational risk and potential for system instability if they do not migrate. The extended security support offers a brief window, but the core message is to initiate and complete the transition to Helm 4 well before February 2027. This impacts DevOps teams, SREs, and anyone responsible for managing applications on Kubernetes using Helm. This move aligns with the broader trend in cloud-native ecosystems where projects evolve rapidly, and older versions eventually reach end-of-life to allow for innovation and address technical debt. Helm 4, released in November 2025, introduced significant architectural improvements to overcome limitations in Helm 3, enabling new features without breaking existing APIs. These improvements include a WebAssembly-based plugin system, `kstatus` integration for deployment monitoring, multi-document values, server-side apply as default, custom template functions, and a stable SDK API. The transition from Helm 3 to Helm 4 is designed to be largely compatible, with most existing Helm 3 charts and releases expected to work with Helm 4 without extensive rewriting. In practice, organizations should immediately begin planning their migration strategy to Helm 4. This involves auditing existing Helm 3 deployments, testing Helm 4 compatibility with current charts, and allocating resources for the upgrade process. While the compatibility is generally good, thorough testing in staging environments is crucial to identify and address any potential breaking changes or unexpected behaviors. Practitioners should leverage the extended security patch window to ensure a smooth transition, but not rely on it as a long-term solution. Proactive migration will safeguard against security vulnerabilities, ensure continued compatibility with evolving Kubernetes environments, and allow teams to leverage the new features and improvements offered by Helm 4.