2.13.1

Latest release in branch 2.13
Released 21 Mar 2019 (7 years ago)

SoftwareHelm
Branch2.13
Status
End of life
Initial release2.13.0
27 Feb 2019 (7 years ago)
Latest patch release2.13.1
21 Mar 2019 (7 years ago)
Active support end15 May 2019 (Ended 6 years, 11 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v2.13.1
Source codehttps://github.com/helm/helm/tree/v2.13.1
Downloadhttps://github.com/helm/helm/releases/tag/v2.13.1
Helm 2.13 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What Is New in Helm 2.13?

Category Highlights
New Features
  • --atomic flag for install/upgrade (auto‑rollback on failure)
  • --render-subchart-notes to show notes from all sub‑charts
  • --devel on helm inspect for pre‑release charts
  • --parallel on helm test to run tests concurrently
  • Chart name validation added to helm lint
Improvements
  • PGP signing of Helm releases
  • Sprig library upgraded to v2.18.0
  • Kubernetes client libraries upgraded to v1.13
  • gRPC updated for more reliable TLS handling
  • Sorted output for helm status
Bug Fixes
  • Correct handling of numeric zero values in --set
  • Respect helm.io/resource-policy: keep during upgrades
  • Fix orphaned replicaset after helm reset --force
  • Allow periods in release names
  • Proper sorting of unknown resource types and namespaces
Security
  • All binaries are now PGP‑signed; verify with the maintainer’s key

Which areas received the biggest updates in Helm 2.13?

CLI Enhancements

The new flags (--atomic, --render-subchart-notes, --devel, --parallel) give developers tighter control over installs, upgrades, and testing. In practice they reduce manual rollback steps and surface more information during a release.

Dependency Refresh

Upgrading Sprig, the Kubernetes client, and gRPC improves template functions and TLS reliability. This matters because charts can now use newer Sprig helpers without pulling custom libraries.

Release Integrity

All Helm binaries are now signed with the maintainer’s PGP key. Teams can integrate signature verification into CI pipelines to ensure the binary hasn’t been tampered with.

Linting and Validation

Adding a chart‑name check to helm lint catches naming errors early, preventing failed releases caused by invalid DNS‑1123 names.

Bug‑Fix Focus

Fixes around zero values, resource‑policy handling, and release‑name parsing address real‑world pain points that surfaced in large‑scale deployments.

FAQ

How does the --atomic flag work?
When you run helm install --atomic or helm upgrade --atomic, Helm will automatically roll back to the previous release if any step fails. This eliminates the need for a manual helm rollback after a broken deployment.

Can I see notes from sub‑charts without installing them?
Yes. Adding --render-subchart-notes to helm install or helm upgrade prints the NOTES.txt of every dependent chart, which is handy for multi‑service applications.

What does the new --devel option do for helm inspect?
It allows you to inspect pre‑release chart versions (e.g., 0.2.0‑alpha.1) directly from the repository, mirroring the behavior of helm fetch --devel.

Is there a way to run chart tests faster?
The --parallel flag on helm test launches multiple test pods at once, cutting down total test time for large charts.

How can I verify the authenticity of the Helm binary?
Download the .asc signature file for your platform and verify it with the maintainer’s PGP key (92AA 783C BAAE 8E3B) using gpg --verify. This step is recommended before upgrading Tiller.

Releases In Branch 2.13

VersionRelease date
2.13.121 Mar 2019
(7 years ago)
2.13.027 Feb 2019
(7 years ago)