2.5.1

Latest release in branch 2.5
Released 24 Jul 2017 (8 years ago)

SoftwareHelm
Branch2.5
Status
End of life
Initial release2.5.0
19 Jun 2017 (8 years ago)
Latest patch release2.5.1
24 Jul 2017 (8 years ago)
Active support end16 Aug 2017 (Ended 8 years, 8 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v2.5.1
Source codehttps://github.com/helm/helm/tree/v2.5.1
Downloadhttps://github.com/helm/helm/releases/tag/v2.5.1
Helm 2.5 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What’s new in Helm 2.5?

Category Highlights
New Features
  • Experimental support for Tiller back‑end plugins (gRPC servers)
  • Array index syntax for --set (e.g. --set servers[0].port=8080)
  • New helm plugin update command
  • --repo flag added to install, upgrade, fetch, etc.
Improvements
  • helm package -u now updates dependencies automatically
  • Package aliasing in requirements.yaml (experimental)
  • Service‑account upgrade via helm init
  • Cache location for downloaded archives moved to $HELM_HOME/cache/archive
Bug Fixes
  • Fixed race conditions in flag parsing
  • Improved handling of hooks across multi‑document manifests
  • Corrected repository URL handling and added atomic file writes
  • Various stability fixes for Windows, Docker images, and plugin management
Breaking Changes
  • helm install and helm upgrade no longer download remote charts to the current directory (use helm fetch instead)
  • Literal keys like "foo[0]" in values.yaml are no longer supported
  • New Force field added to gRPC calls – may affect custom Tiller forks

Which areas received the biggest changes in Helm 2.5?

Experimental Tiller plugins

Helm now lets you run Tiller as a gRPC server plugin. The feature is gated behind the --experimental-release flag, so you can try it without affecting production clusters.

CLI enhancements

The --set flag understands array indexes, making complex value overrides easier. The new --repo flag lets you point commands at a specific chart repository without altering helm repo add state.

Dependency handling

Packaging now automatically pulls in missing dependencies (helm package -u). You can also alias dependencies in requirements.yaml, which helps when the same chart is needed under different names.

Service‑account and RBAC upgrades

helm init --upgrade can now replace Tiller’s service account, simplifying migrations on clusters that enforce RBAC.

Repository and caching changes

Downloaded archives are stored under $HELM_HOME/cache/archive, keeping the workspace tidy. The helm plugin update command makes plugin maintenance straightforward.

For the full documentation, see the Helm docs.

FAQ

How do I enable the experimental Tiller plugin system?
Start Tiller with the --experimental-release flag; then register your gRPC server as a plugin. This keeps the feature opt‑in until it graduates.

Can I still use helm install to fetch a chart locally?
No. helm install now streams the chart directly to the cluster. Use helm fetch if you need a local copy.

What’s the correct way to override an array element in a values file?
Pass the index in the --set flag, e.g. helm install mychart --set servers[0].port=8080. Literal keys like "servers[0]" in values.yaml are no longer parsed.

Do I need to change anything for RBAC‑enabled clusters?
Run helm init --upgrade to replace Tiller’s service account with one that has the proper RoleBindings. This avoids permission errors on Kubernetes 1.6+.

How do I update a Helm plugin to the latest version?
Execute helm plugin update <plugin-name>. The command checks the plugin’s repository and replaces the binary if a newer release exists.

Releases In Branch 2.5

VersionRelease date
2.5.124 Jul 2017
(8 years ago)
2.5.019 Jun 2017
(8 years ago)