What Is New in Helm 2.16?
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Deprecations | None in this release. |
What are the main changes in Helm 2.16?
Kubernetes 1.16 compatibility
Helm now understands the new manifest apiVersion values introduced in Kubernetes 1.16. This matters because charts can target the latest cluster without manual edits.
Sprig template library upgrade
The bundled Sprig functions were moved to version 2.22, adding several new helpers and fixing edge‑case bugs. In practice, chart authors gain access to more robust templating utilities.
Cross‑device rename support
Helm’s internal file operations now handle renames that cross filesystem boundaries. This reduces failures when charts are unpacked on heterogeneous storage.
Search command version display fix
The helm search output now correctly shows the chart’s version instead of the repository version, making it easier to verify what you are about to install.
Tiller upgrade path
After installing the client, run helm init --upgrade to bring the server component (Tiller) to the 2.16 binaries. This step is required for the new features to be available on the cluster.
Miscellaneous bug fixes and clean‑ups
Numerous issues were addressed, including a race condition in the kube client, incorrect ingress checks during helm wait, and improved handling of symbolic links. The codebase also received formatting and license updates.
FAQ
How do I upgrade Tiller to the 2.16 version?
Run helm init --upgrade on a machine that has the 2.16 client installed. The command replaces the existing Tiller pod with the new binary.
Does Helm 2.16 work with Kubernetes 1.16 API objects?
Yes, the client now recognises the new apiVersion strings, so charts targeting apps/v1, networking.k8s.io/v1, etc., install without manual changes.
What changed in the output of helm search?
The table now lists the chart’s actual version column, eliminating the previous mismatch where the repository version was shown.
Are there any breaking changes I need to watch for?
There are no deprecations in this release, but upgrading Tiller is required to access the new features. Existing charts continue to work unchanged.
How can I verify the integrity of the downloaded binaries?
Each release archive is signed; download the corresponding .asc file and verify it with the GPG key 4614 49C2 5E36 B98E. See the official Helm documentation for the verification steps.
For more details, refer to the Helm documentation.