Helm 3 Reaches End-of-Life Milestone, Urging Migration to Helm 4 for Continued Support

The Helm project has officially marked Helm v3.22.0 as the last minor release for the Helm 3 line, released on September 10, 2026. This means that Helm 3 will no longer receive bug fixes and will only be supported with security patches until February 10, 2027. This announcement, while not unexpected given the release of Helm 4 in late 2025, serves as a firm deadline for organizations still utilizing Helm 3 in their Kubernetes environments. This development is significant for anyone managing applications on Kubernetes using Helm. The cessation of bug fixes means that any non-security-related issues discovered in Helm 3 after September 10, 2026, will not be addressed. More critically, the hard stop on security patches in February 2027 leaves Helm 3 users vulnerable to potential exploits if they do not migrate. Platform engineers, DevOps teams, and Kubernetes administrators are directly affected, as they are responsible for the stability and security of their deployments. This end-of-life timeline for Helm 3 aligns with the broader trend in cloud-native ecosystems where projects evolve rapidly, and older versions are sunsetted to focus resources on newer, more capable iterations. The release of Helm 4 in November 2025, coinciding with Helm's 10th anniversary, introduced significant updates aimed at addressing modern Kubernetes challenges, including CI/CD complexity, enhanced security features like chart verification and signed packages, and improved multi-cluster support. The move to Helm 4 also brought in a WebAssembly-based plugin system and server-side apply as default, reflecting the increasing maturity and demands of cloud-native application management. In practice, practitioners should prioritize developing and executing a migration plan to Helm 4. While the transition from Helm 3 to Helm 4 is designed to be smoother than the Helm 2 to Helm 3 upgrade, with existing Helm 3 charts and releases generally compatible, there are breaking changes to be aware of, particularly concerning `--wait` flag behavior, post-renderers (now plugins), and CI/CD scripts. Teams should thoroughly test their existing charts and deployment pipelines with Helm 4 in staging environments. It is advisable to consult the official Helm documentation and community resources for detailed migration guides and best practices to ensure a low-risk and plannable switch before the security patch window closes in early 2027.