Helm 3 Reaches Feature Freeze as v3.22.0 Ships Alongside Helm 4.3.0

The CNCF Helm project has reached a definitive milestone in its lifecycle management with the rollout of Helm v4.3.0 and the subsequent release of Helm v3.22.0, officially closing feature development for the Helm 3 branch. Under the revised lifecycle timeline defined in HIP-0012, Helm 3.22.0 serves as the final minor release intended primarily to deliver upstream Kubernetes client library compatibility. Going forward, Helm 3 enters a strict security-only maintenance phase that concludes on February 10, 2027, after which all project support ceases entirely. This transition has immediate operational implications for DevOps practitioners and platform platform teams managing Kubernetes fleet deployments. Helm 3 has served as the baseline packaging standard for more than six years, establishing deep integration into continuous delivery pipelines, GitOps engines like Argo CD, and public chart registries. The freeze on feature development and client library updates means that future Kubernetes releases (beyond current client version mappings) will not be officially validated against Helm 3 binaries. Teams that delay transitioning risk encountering client-side drift, unpatched schema mismatches, and deprecated API incompatibilities in cluster automation. Contextually, this milestone underscores the maturation of Helm 4 as the long-term packaging standard across cloud-native environments. Helm 4 addresses foundational technical debt accumulated across Helm 3 by introducing architectural modernizations such as a stable SDK API, native integration with kstatus deployment health monitoring, default Server-Side Apply (SSA) semantics, and WebAssembly (Wasm)-based extensibility for plugins and renderers. As GitOps and platform engineering practices increasingly demand deterministic release reconciliation and drift detection, standardizing on Helm 4's modernized core becomes essential. In practice, engineering leaders should inventory active Helm installations across CI/CD runners, local workstations, and orchestrators. While existing Helm 3 chart definitions remain largely backward-compatible with Helm 4 execution runtimes, tooling upgrades must be audited for CLI flag changes, plugin runtime dependencies, and registry authentication updates. Platform teams should treat the February 2027 security cutoff not as a distant milestone, but as an operational mandate to benchmark, validate, and standardize cluster workloads on the Helm 4 series throughout the upcoming upgrade cycles.