2.11.0

Latest release in branch 2.11
Released 25 Sep 2018 (7 years ago)

SoftwareHelm
Branch2.11
Status
End of life
Initial release2.11.0
25 Sep 2018 (7 years ago)
Latest patch release2.11.0
25 Sep 2018 (7 years ago)
Active support end07 Dec 2018 (Ended 7 years, 4 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v2.11.0
Source codehttps://github.com/helm/helm/tree/v2.11.0
Downloadhttps://github.com/helm/helm/releases/tag/v2.11.0
Helm 2.11 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What Is New in Helm 2.11 (summary table)

Category Highlights
New Features
  • Kubernetes v1.11 support
  • Added --tls-hostname flag for Tiller TLS connections
  • New helm notes command to display chart notes
  • Release list can be sorted by chart name (helm list --chart-name)
  • TLS flags can be set via environment variables
  • Hidden password prompt for helm repo add --username without --password
  • Zsh autocompletion can be auto‑loaded by compinit
  • helm create now adds release labels that follow SIG Apps conventions
Improvements
  • Proxy environment variables are now respected
  • Fixed race condition in helm init --wait
  • Enhanced fake client for testing upgrades and rendering
  • Improved handling of repository credentials during dependency operations
  • Auto‑loading of Zsh completions simplifies shell setup
Bug Fixes
  • Lint no longer fails when a required value is missing
  • helm list now shows all releases in a chunk
  • Fixed TLS flag parsing regression
  • Resolved issue where local Tiller ignored kubectl auth‑provider plugins
  • Corrected handling of empty values in releases
  • Fixed credential handling for helm dependency build/update
Security
  • Hidden password input improves credential safety
  • TLS hostname verification added via --tls-hostname
  • Environment‑driven TLS flags reduce exposure of secrets in command lines
Deprecated None for this release

What new Kubernetes compatibility does Helm 2.11 provide?

Helm 2.11 adds official support for Kubernetes v1.11, meaning chart rendering and Tiller communication have been validated against the latest API groups and resource versions. In practice this reduces version‑skew errors when you upgrade your cluster.

How does Helm 2.11 enhance TLS handling and security?

The release introduces a --tls-hostname flag, allowing you to verify the server name presented by Tiller’s TLS certificate. TLS flags can now be supplied through environment variables, keeping secrets out of shell history. Hidden password prompts for repository authentication also prevent accidental exposure.

Which usability improvements were added for chart developers?

helm create now stamps release labels that follow the SIG Apps naming conventions, helping downstream tooling categorize releases. The new helm notes command surfaces the NOTES.txt section of a chart without a full install, and sorting releases by chart name makes large release lists easier to navigate.

What stability fixes should I verify after upgrading to Helm 2.11?

Key fixes include proper handling of proxy variables, a race condition fix in helm init --wait, and corrected behavior when required template values are missing. The helm list command now correctly paginates all releases, and dependency commands respect repository credentials.

How does Helm 2.11 improve shell completion experience?

Zsh users can now have Helm completions auto‑loaded by simply running compinit. This removes the need for manual sourcing of completion scripts and aligns Helm’s behavior with other popular CLI tools.

FAQ

Can I use Helm 2.11 with an existing Helm 2.10 release history?
Yes, the upgrade is backward compatible; existing releases remain accessible and no migration steps are required beyond running helm init --upgrade.

Do I need to rebuild my charts to target Kubernetes 1.11?
No, charts built for earlier versions continue to work, but you may want to test them against the new API versions to catch deprecations.

How do I enable the new TLS hostname verification?
Pass --tls-hostname my-tiller.example.com to any Helm command that communicates with Tiller over TLS.

What is the best way to provide repository credentials without exposing passwords?
Use helm repo add --username user and let Helm prompt for the password, or set the credentials via environment variables and rely on the hidden prompt feature.

Will the new helm notes command affect my CI pipelines?
It can simplify CI scripts by allowing you to fetch chart notes without a full install, reducing resource consumption and execution time.

Releases In Branch 2.11

VersionRelease date
2.11.025 Sep 2018
(7 years ago)