Last checked and updated on 04 May 2026
What Is New in Helm 3.1?
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security | None specific to this release; existing verification mechanisms (GPG signatures, shasums) remain unchanged. |
| Deprecated | No features were deprecated in this version. |
For a full list of changes, see the official release notes.
What are the major change groups in Helm 3.1?
Post‑render hooks
Hooks run after the normal rendering phase, allowing you to pipe the output through an external program. This is handy for injecting custom annotations or performing policy checks before the resources hit the cluster.
CLI ergonomics
The command line got cleaner: -A for all namespaces, restored --description, and a Go‑based completion engine that no longer pulls in kubectl. Autocompletion is faster and works out‑of‑the‑box on all supported shells.
Template engine enhancements
Templates can now reference the release name directly, and the rendering order follows the file system layout before any internal sorting. Recursion limits were tightened to avoid runaway loops.
Packaging and linting
helm lint accepts a packaged .tar.gz chart, making CI pipelines simpler. Each binary download includes a .sha256sum file, so you can verify integrity with a single command.
Bug‑fix focus
Numerous edge‑case bugs were squashed: namespace handling for helm template, memory driver consistency, CRD processing, and chart‑lock digest mismatches. These fixes improve stability across diverse environments.
FAQ
How do I enable post‑render hooks in my chart?
Define a hook of type post-render in templates/ and point the helm install command to an executable with --post-renderer. The renderer receives the full manifest on stdin and must write the transformed manifest to stdout.
Can I still use kubectl for shell completion?
Yes, but it is no longer required. Helm now ships its own Go‑based completion scripts for Bash, Zsh, and Fish, which you can source directly from the binary.
What does the restored --description flag do?
It lets you attach an arbitrary text note to a release. The description appears in helm history and can be queried with helm status --output json.
Is the new .sha256sum file compatible with my CI tools?
Absolutely. Run sha256sum -c helm-v3.1.0-linux-amd64.tar.gz.sha256sum (or shasum -a 256 -c on macOS) to verify the download before extracting.
Do the template recursion fixes affect existing charts?
Only charts that relied on deep recursive includes will see a stricter limit. Most charts are unaffected, but if you hit a max recursion depth exceeded error, refactor the includes to be shallower.