โ ๏ธ Breaking Change
Impact Score: 7/10
Helm 2.7.2 is a Security Fix
Source available โ automated, not human-reviewed
Component: helm ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
Breaking-change evidence from the source
Breaking Changes This release places much more stringent requirements on certificate auth. It is
โก Executive Summary (TL;DR)
Helm v2.7.2. Source highlight: Helm v2.7.2 is a security release and bug release. Users are strongly encouraged
Who Does This Impact? (Role-Based Analysis)
๐ป Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
๐ Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
โ๏ธ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
โ ๏ธ Breaking Changes & Deprecations (1)
- Breaking Changes This release places much more stringent requirements on certificate auth. It is
๐ง Bug Fixes & Patches (3)
- `#helm-dev` for discussing PRs, code, and bugs
- Test, debug, and contribute charts: GitHub/kubernetes/charts
- fix(helm): fix missing ssl params (#3152) e8e6ac5d7783808cc0bd1adad053bec339849647 (Matt Butcher)
๐ View Raw Release Notes (Original Developer Log)
Helm v2.7.2 is a security release and bug release. Users are strongly encouraged
to upgrade.
The Helm Core Maintainers discovered a bug in TLS handling. Versions of Tiller
prior to 2.7.1 had a certificate verification policy that allowed self-signed
certificates to pass the server-side certificate verification phase.
This release contains a fix that *requires* the client certificate to be verified
against Tiller's CA.
Additionally, this release adds documentation for configuring strong gRPC authentication
using TLS. While this feature has been available since 2.3.0, it was not properly
documented.
Finally, this release contains several TLS-related fixes to Helm CLI commands, adding TLS
parameters back to the `helm get *` verbs, and fixing `helm list --tls`.
The community keeps growing, and we'd love to see you there.
- Join the discussion in [Kubernetes Slack](https://slack.k8s.io/):
- `#helm-users` for questions and just to hang out
- `#helm-dev` for discussing PRs, code, and bugs
- Hang out at the Public Developer Call: Thursday, 9:30 Pacific via [Zoom](https://zoom.us/j/4526666954)
- Test, debug, and contribute charts: [GitHub/kubernetes/charts](https://github.com/kubernetes/charts)
## Breaking Changes
This release places much more stringent requirements on certificate auth. It is
possible that some misconfigured Helm SSL configurations that were working are now
broken.
## Installation and Upgrading
Download Helm 2.7.2. The common platform binaries are here:
- [OSX](https://get.helm.sh/helm-v2.7.2-darwin-amd64.tar.gz)
- [Linux](https://get.helm.sh/helm-v2.7.2-linux-amd64.tar.gz)
- [Windows](https://get.helm.sh/helm-v2.7.2-windows-amd64.tar.gz)
Once you have the client installed, upgrade Tiller with `helm init --upgrade`.
The [Quickstart Guide](https://docs.helm.sh/using_helm/#quickstart-guide) will get you going from there. For **upgrade instructions** or detailed installation notes, check the [install guide](https://docs.helm.sh/using_helm/#installing-helm). You can also use a [script to install](https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get) on any system with `bash`.
## Changelog
- fix(helm): fix missing ssl params (#3152) e8e6ac5d7783808cc0bd1adad053bec339849647 (Matt Butcher)