2.12.3

Latest release in branch 2.12
Released 22 Jan 2019 (7 years ago)

SoftwareHelm
Branch2.12
Status
End of life
Initial release2.12.0
07 Dec 2018 (7 years ago)
Latest patch release2.12.3
22 Jan 2019 (7 years ago)
Active support end27 Feb 2019 (Ended 7 years, 2 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v2.12.3
Source codehttps://github.com/helm/helm/tree/v2.12.3
Downloadhttps://github.com/helm/helm/releases/tag/v2.12.3
Helm 2.12 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What Is New in Helm 2.12 – Summary Table

Category Key Highlights
New Features
  • Environment variable HELM_KEY_PASSPHRASE for chart signing
  • Built‑in helm convert plugin
  • JSON/YAML output option for helm get values
  • Support for repository URLs without a trailing slash
  • Optional --no-sudo flag for Tiller installation
Improvements
  • Linter now returns an empty string for missing required fields
  • Custom resources can be used in hook definitions
  • Release pruning never removes the last deployed revision
  • Nested values are merged correctly on upgrade
  • Documentation refreshed (helmignore, license file, provenance)
Bug Fixes
  • Fixed line‑break handling for custom resources and pod status output
  • Resolved CRD deletion issue with crd-install hook
  • Corrected out‑of‑order list handling for --set
  • Addressed race condition in helm list
  • Multiple Windows‑specific test failures repaired
Security & Docs
  • Local‑only Tiller execution guidance
  • Provenance docs updated for new GnuPG format
  • RBAC usage notes added to documentation

For the full changelog see the Helm 2.12 release notes.

What new features does Helm 2.12 bring to chart authors?

Key additions

  • Signing support via HELM_KEY_PASSPHRASE – you can now protect chart integrity without extra tooling.
  • The helm convert plugin simplifies migration from other package formats.
  • helm get values now accepts --output json|yaml, making automation scripts cleaner.
  • Repository URLs no longer need a trailing slash, reducing common copy‑paste errors.
  • The new --no-sudo flag lets you install Tiller in environments where sudo is unavailable.

How has Helm 2.12 been improved for reliability?

Stability enhancements

  • Linter now returns an empty string instead of nil for missing required fields, preventing unexpected crashes.
  • Custom resources are now accepted in hook definitions, expanding hook use cases.
  • Release pruning logic was hardened – the last deployed revision is never deleted.
  • Nested values are merged correctly during upgrades, avoiding silent configuration loss.
  • Documentation around .helmignore, license files, and provenance has been clarified.

Which bugs were fixed in Helm 2.12?

Selected bug fixes

  • Line‑break handling for custom resources and pod status output corrected.
  • CRD deletion bug with crd-install hook resolved.
  • Out‑of‑order list values via --set now work as expected.
  • Race condition in helm list eliminated, improving concurrent usage.
  • Windows test suite failures fixed, ensuring cross‑platform reliability.

What security‑related changes are included?

Security and documentation updates

  • Chart signing via HELM_KEY_PASSPHRASE adds a lightweight integrity check.
  • Guidance for running Tiller locally only reduces exposure surface.
  • Provenance documentation now reflects the new GnuPG format, helping teams adopt modern signing practices.
  • RBAC considerations are highlighted, aiding secure cluster configurations.

FAQ

Can I use helm init --upgrade without sudo?
Yes – add the --no-sudo flag and Helm will skip any sudo calls during Tiller installation.

How do I sign a chart with the new environment variable?
Set HELM_KEY_PASSPHRASE to your GPG passphrase before running helm package; Helm will automatically sign the chart.

Does the helm get values output option replace the old --output flag?
The new option extends the command; you can now choose json or yaml directly, which is useful for CI pipelines.

Will pruning releases ever delete the last successful revision?
No – the pruning logic was updated to keep the most recent deployed revision, preventing accidental loss of the only working version.

Are custom resources now fully supported in hook definitions?
Yes – you can declare any Kubernetes custom resource in helm.sh/hook annotations, and Helm will process them correctly.

Releases In Branch 2.12

VersionRelease date
2.12.322 Jan 2019
(7 years ago)
2.12.007 Dec 2018
(7 years ago)