2.14.3

Latest release in branch 2.14
Released 30 Jul 2019 (6 years ago)

SoftwareHelm
Branch2.14
Status
End of life
Initial release2.14.0
15 May 2019 (6 years ago)
Latest patch release2.14.3
30 Jul 2019 (6 years ago)
Active support end18 Oct 2019 (Ended 6 years, 6 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v2.14.3
Source codehttps://github.com/helm/helm/tree/v2.14.3
Downloadhttps://github.com/helm/helm/releases/tag/v2.14.3
Helm 2.14 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What Is New in Helm 2.14?

Category Key Changes
New Features
  • Annotation helm.sh/resource-policy: delete to opt‑in to resource deletion
  • Tiller flag --probe-listen for custom probe address:port
  • Rollback flag --cleanup-on-fail to remove resources created by a failed rollback
  • helm get now supports --template for custom output formatting
Improvements
  • Go upgraded to v1.12
  • Kubernetes client libraries updated to v1.14
  • semver library upgraded to v1.4
  • Added ProGet as a supported chart repository host
Bug Fixes
  • Corrected spurious “ROLLING BACK” messages when --atomic is not set
  • CRD install hook now waits for the CRD to reach the Established state
  • Scaffold chart created by helm create installs correctly
  • helm reset --force no longer hangs if the Tiller pod is already removed
  • Zsh completion fixed for macOS
  • Numerous stability and validation fixes across the code base
Security Release signed with GPG key 6EA5 D759 8529 A53E (verification instructions in the release assets)
Deprecated None reported in this release

For full details, see the Helm documentation.

What new features does Helm 2.14 bring?

Resource‑policy annotation

The helm.sh/resource-policy: delete annotation lets you mark a manifest for deletion when the release is removed, giving fine‑grained control over cleanup.

Tiller probe listener

With --probe-listen you can expose a custom address and port for health probes, which is handy for monitoring setups that require non‑default endpoints.

Rollback cleanup‑on‑fail

The --cleanup-on-fail flag on helm rollback automatically deletes any resources created during a rollback that subsequently fails, keeping the cluster tidy.

Custom templating for helm get

Use helm get <release> --template "{{ .Chart.Name }}" to format output with any Go template you need, removing the need for post‑processing scripts.

Which dependencies were updated in Helm 2.14?

  • Go runtime upgraded to version 1.12, improving compilation speed and compatibility.
  • Kubernetes client libraries moved to v1.14, aligning Helm with newer API versions.
  • semver library updated to v1.4, fixing edge‑case version parsing.
  • Added support for ProGet as a chart repository, expanding the range of hosted chart sources.

What command‑line enhancements are included?

  • helm get now accepts --template for on‑the‑fly formatting.
  • Tiller’s --probe-listen flag enables custom health‑check endpoints.
  • Rollback gains --cleanup-on-fail to automatically purge failed rollback artifacts.
  • Various help messages were clarified and made more user‑friendly.

What bugs were fixed in this release?

  • Removed incorrect “ROLLING BACK” logs when --atomic is not set.
  • CRD install hooks now wait for the CRD to become Established before proceeding.
  • Scaffold charts generated by helm create install without errors.
  • helm reset --force no longer hangs if the Tiller pod has already been deleted.
  • Zsh completion scripts fixed for macOS compatibility.
  • Multiple internal validation and stability issues were resolved.

FAQ

How do I enable automatic deletion of resources when a release is removed?
Add the annotation helm.sh/resource-policy: delete to the manifest you want Helm to delete on release purge.

Can I change the address Tiller uses for health probes?
Yes, start Tiller with --probe-listen=<host>:<port> to bind the probe endpoint to a custom address.

What does the --cleanup-on-fail flag do during a rollback?
If the rollback fails, Helm will automatically delete any new resources that were created as part of that rollback attempt.

How can I format the output of helm get without writing a separate script?
Use the --template flag with any valid Go template, e.g. helm get myrel --template "{{ .Chart.Name }}".

Do I need to upgrade Tiller after installing Helm 2.14?
Run helm init --upgrade to bring the Tiller deployment to the new version and take advantage of the added flags and fixes.

Releases In Branch 2.14

VersionRelease date
2.14.330 Jul 2019
(6 years ago)
2.14.015 May 2019
(6 years ago)