What Is New in Helm 3.7 – Quick Summary
| Category | Key Highlights |
|---|---|
| New Commands / Flags |
|
| OCI Experimental Overhaul |
|
| Template Engine Enhancements |
|
| Signal & Process Handling |
|
| Other Improvements |
|
What are the major change groups in Helm 3.7?
OCI experimental commands were streamlined
The OCI workflow now uses the core helm pull, helm push, and helm package commands. Legacy helm chart * helpers were removed, and the manifest format changed, so existing OCI charts need to be rebuilt.
CLI gained several new flags and sub‑commands
Uninstall can now wait for resource deletion, helm show crds lets you inspect CRDs quickly, and repository commands got password‑stdin support and selective updates.
Template engine got a root‑chart indicator
The .Chart.IsRoot variable helps sub‑chart templates decide whether they are the top‑level chart, simplifying conditional logic.
Graceful handling of termination signals
Both install and upgrade now listen for SIGTERM, which is useful in CI pipelines that may cancel jobs.
Dependency and repository tooling improvements
Column width control for helm dependency list, optional repo name for helm repo update, and updated completion scripts make day‑to‑day usage smoother.
FAQ
How do I migrate my existing OCI charts after upgrading to Helm 3.7?
Re‑package each chart with helm package and push it again using helm push. The new manifest format is not backward compatible.
Can I still use helm chart pull in scripts?
No. Replace it with helm pull. The command signature is identical, so most scripts only need a name change.
What does helm uninstall --wait actually wait for?
It blocks until all Kubernetes objects created by the release are fully removed, respecting the --timeout value you provide.
Is the new .Chart.IsRoot variable safe to use in all charts?
Yes. It evaluates to true only for the top‑level chart, allowing you to write shared templates that behave differently in sub‑charts.
Do the signal handling changes affect Helm’s behavior in Helm 3.6?
The SIGTERM handling is new to 3.7; earlier versions would terminate immediately, potentially leaving resources dangling.