What Is New in Helm 2.6
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security / Reliability |
|
| Deprecated | None reported for this release. |
How Does Helm 2.6 Improve Manifest Handling?
Helm now orders resources of the same kind alphabetically, which reduces nondeterministic apply order. The kind sorter also places unknown kinds and APIService objects in a predictable sequence. In practice this makes helm install output more repeatable across clusters.
What CLI Enhancements Were Added?
The -a flag on helm list exposes every release, not just the latest per name. Support for HELM_HOME during plugin loading simplifies custom plugin paths. Documentation for the new helm-edit plugin guides users on extending Helm’s functionality.
Which Chart‑Related Fixes Matter Most?
Requirements handling received several updates: the requirements.yaml file is now part of the chart structure, and charts can delete secrets automatically on reset. These changes keep dependency graphs clean and reduce manual cleanup after upgrades.
How Were Internal Refactors Reflected in the Release?
Numerous packages (e.g., pkg/chartutil, pkg/strvals) were refactored for clearer comments, fewer map lookups, and better error handling. Test suites were expanded, improving confidence in future releases.
What Stability Fixes Were Introduced?
Bug fixes span flag parsing, plugin loading, and the helm get command family. The removal of the Tiller lock system eliminates a source of deadlocks, relying on the storage backend’s native concurrency controls.
FAQ
How do I list every release with Helm 2.6?
Use helm list -a. The -a flag shows all releases, including superseded ones.
Is there any change to how values with leading zeros are parsed?
Yes. The parser now preserves leading zeros, so --set version=01.02 retains the exact string.
Do I need to upgrade Tiller after installing Helm 2.6?
Run helm init --upgrade to replace the old Tiller binary with the 2.6 version.
What should I do about the removed Tiller lock system?
Nothing special; the backend storage now handles concurrency, so you can continue using Helm as before.
How can I clean up secrets left by a previous Helm installation?
Execute helm reset; the command now deletes the associated secret automatically.