Helm 3 End-of-Life Looms: Practitioners Urged to Accelerate Helm 4 Migration

The Helm project has officially marked September 10, 2026, as the date of the last minor release for Helm 3 (v3.22.0), which primarily included dependency updates and Kubernetes client library upgrades to support newer Kubernetes versions. Bug fixes for Helm 3 have now ceased, and critically, security patches will only be provided until February 10, 2027. This definitive timeline underscores the urgency for all users to transition to Helm 4, which saw its general availability release in November 2025 and is currently at version 4.3.0 as of September 9, 2026. This development is significant for anyone managing Kubernetes applications with Helm. Continuing to use Helm 3 beyond February 2027 will expose deployments to unpatched security vulnerabilities, a risk that is unacceptable in production environments. The move to Helm 4 is essential for maintaining a secure and supportable Kubernetes ecosystem. While the migration from Helm 2 to Helm 3 was notoriously challenging, the project maintainers have designed Helm 4 to be considerably more compatible, aiming for a smoother transition for existing releases. This end-of-life announcement aligns with the broader trend in cloud-native development towards continuous evolution and the deprecation of older tooling to foster innovation and improve security. As Kubernetes itself progresses rapidly, its ecosystem tools like Helm must keep pace. The introduction of Helm 4 with features like improved multi-cluster and CI/CD support, along with enhanced security features such as chart verification and signed packages, reflects the growing maturity and demands of enterprise-scale Kubernetes deployments. The project's focus on Server-Side Apply in Helm 4 also indicates a move towards more predictable deployments and better handling of configuration drift, addressing common pain points for practitioners. In practice, practitioners should immediately begin assessing their Helm 3 usage. While Helm 4 is designed to be largely compatible with existing Helm 3 charts and releases, it does introduce breaking changes that require attention. Key areas to focus on include changes to the `--wait` flag behavior, post-renderers, and certain CI/CD script adjustments. It's crucial to test existing charts and workflows thoroughly using `helm template`, `helm upgrade --dry-run`, and actual upgrades in staging environments to identify and address any potential issues early. Updating RBAC configurations to include the `watch` verb where `--wait` is used, adjusting CI/CD scripts for renamed flags, and reconfiguring post-renderers as plugins are concrete steps to take. Furthermore, teams should familiarize themselves with Helm 4's OCI registry workflows and update any custom SDK usage to the `helm.sh/helm/v4` import path. The extended security support until February 2027 provides a window for a controlled and planned migration, but delaying this process is no longer a viable option.