3.4.2

Latest release in branch 3.4
Released 09 Dec 2020 (5 years ago)

SoftwareHelm
Branch3.4
Status
End of life
Initial release3.4.0
26 Oct 2020 (5 years ago)
Latest patch release3.4.2
09 Dec 2020 (5 years ago)
Supported
Kubernetes versions		1.19.x - 1.16.x
Active support end13 Jan 2021 (Ended 5 years, 3 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v3.4.2
Source codehttps://github.com/helm/helm/tree/v3.4.2
Downloadhttps://github.com/helm/helm/releases/tag/v3.4.2
Helm 3.4 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What Is New in Helm 3.4?

Category Highlights
Repository handling
  • Stable & incubator repositories are archived; Helm now detects legacy URLs and prompts users to switch.
  • Top‑level annotations field added to index.yaml for extra metadata.
CLI enhancements
  • helm status gains a --show-descriptions flag.
  • helm list now supports a --time-format flag for custom timestamp rendering.
  • Improved error messages when old repository URLs are used.
Linting & validation
  • helm lint checks chart dependencies.
  • Name‑length validation added; overly long release names are reported.
Security / signing
  • Support for passing a signing passphrase via file or stdin (PR #8394).
Bug fixes
  • Various fixes around time‑format handling, linting edge cases, and repository URL rewrites.

Which areas got the biggest updates in Helm 3.4?

Repository handling

Helm now treats the historic stable and incubator chart repos as archived locations. When a user references the old URL, Helm prints a clear migration hint and points to the new archive. This prevents silent failures when the upstream index disappears.

CLI usability

The addition of --show-descriptions to helm status and --time-format to helm list gives operators more control over output without needing external tooling. In practice, teams can script Helm output directly into dashboards or alerts.

Chart quality checks

helm lint now validates dependency declarations and enforces a maximum name length. Early detection of these issues reduces failed releases and keeps CI pipelines fast.

Security & signing

Passing a signing passphrase from a file or stdin makes automated CI/CD signing more secure, avoiding hard‑coded secrets in scripts.

For a quick start with the new version, see the Helm Quickstart Guide.

FAQ

How do I migrate from the old stable/incubator repo?
Run helm repo add with the new archive URL; Helm will automatically warn you if you still reference the legacy URL.

Can I customize timestamps in helm list?
Yes, use helm list --time-format "2006-01-02 15:04:05" to specify any Go time layout.

What does the --show-descriptions flag do?
It prints the description field from the release’s notes alongside the status output, giving more context without opening the full notes.

Will helm lint fail my CI if a chart has a long name?
Starting with 3.4, any release name exceeding Helm’s length limit triggers a lint error, so you should keep names concise.

How can I sign a chart without exposing the passphrase?
Store the passphrase in a protected file or pipe it via stdin and invoke Helm with --sign --key mykey --pass-phrase-file /path/to/file.

Releases In Branch 3.4

VersionRelease date
3.4.209 Dec 2020
(5 years ago)
3.4.026 Oct 2020
(5 years ago)