2.0.2

Latest release in branch 2.0
Released 06 Dec 2016 (9 years ago)

SoftwareHelm
Branch2.0
Status
End of life
Initial release2.0.0
16 Nov 2016 (9 years ago)
Latest patch release2.0.2
06 Dec 2016 (9 years ago)
Active support end13 Dec 2016 (Ended 9 years, 4 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v2.0.2
Source codehttps://github.com/helm/helm/tree/v2.0.2
Downloadhttps://github.com/helm/helm/releases/tag/v2.0.2
Helm 2.0 ReleasesView full list
SEE ALSO: Kubernetes Kubernetes New Terraform Terraform New

What Is New in Helm 2.0

Category Highlights
New Features
  • Release names can now be up to 53 characters.
  • Tiller logs include the originating source file.
  • Chart bucket URLs switched from path‑based to domain‑based format.
  • Gometalinter upgraded to versioned releases.
  • Dry‑run mode now prints YAML parsing errors with the offending data.
Improvements
  • Upgrade operations correctly purge fields removed from manifests.
  • helm delete respects the --dry-run flag.
  • helm create no longer overwrites existing files.
  • Repository entries are replaced instead of duplicated on add.
  • Documentation expanded (YAML techniques, chart template guide, install FAQ).
Bug Fixes
  • Fixed incomplete patch generation on updates.
  • Corrected value references in boilerplate NOTES.txt.
  • Resolved linter errors and increased script deadline.
  • Adjusted deployment name in the Tiller delete command.
  • Ensured proper handling of TLS when downloading Helm and charts.
Security
  • Switched checksum generation to openssl instead of shasum.
  • All chart and binary downloads now enforce HTTPS.
Deprecated None for this release.

Reference: Helm 2.0 release notes

What are the major new capabilities introduced?

Longer release names

Helm now accepts names up to 53 characters, reducing the need for manual truncation in large clusters.

Enhanced Tiller logging

Each log entry includes the source file, making debugging faster because you can jump straight to the offending code.

Domain‑based chart bucket URLs

Charts are served from mybucket.storage.googleapis.com style URLs, which aligns with CDN best‑practice and simplifies DNS configuration.

Improved dry‑run experience

Running helm install --dry-run --debug now prints the exact YAML that failed to parse, so you can fix template errors before any resources are created.

What improvements make day‑to‑day usage smoother?

  • Upgrade commands now clean up fields that were removed from the chart, preventing stale configuration from lingering.
  • helm delete respects --dry-run, letting you preview deletions safely.
  • helm create safeguards existing files, avoiding accidental overwrites.
  • Repository handling now replaces duplicate entries, keeping helm repo list tidy.
  • Documentation added for YAML techniques and chart templating, reducing the learning curve for new users.

Which bugs were fixed that developers should be aware of?

  • Patch generation on updates now produces complete manifests.
  • Value references in NOTES.txt are corrected, ensuring post‑install messages display accurate information.
  • Linter warnings have been cleared, and the linter script timeout increased to avoid false failures.
  • The deployment name used in the Tiller delete command was fixed, preventing accidental removal of the wrong release.
  • HTTPS is now enforced for all Helm binary and chart downloads, eliminating insecure HTTP fallback.

What security enhancements are included?

  • Checksum generation switched to openssl, which is universally available on supported platforms.
  • All network traffic for Helm binaries and chart archives is forced over HTTPS, protecting against man‑in‑the‑middle tampering.

FAQ

Can I still use short release names?
Yes, short names continue to work; the limit simply raises the ceiling to 53 characters.

How do I see which file generated a Tiller log entry?
Each log line now includes a source=file.go:line suffix, so you can open that file directly.

Will helm upgrade delete resources that I removed from the chart?
Upgrades now purge fields that disappear from the manifest, ensuring the cluster matches the chart exactly.

What should I do if helm install --dry-run --debug shows a YAML parse error?
Review the printed YAML snippet in the output; it contains the offending section, allowing you to correct the template before a real install.

Do I need to change my chart repository URLs after the bucket domain change?
Yes, update any hard‑coded .../bucket/path URLs to the new domain‑style format to avoid 404 errors.

Releases In Branch 2.0

VersionRelease date
2.0.206 Dec 2016
(9 years ago)
2.0.016 Nov 2016
(9 years ago)