Last checked and updated on 04 May 2026
What Is New in Helm 2.17 (summary table)
| Category | Key Changes |
|---|---|
| New Features | Added --skip-refresh flag to helm init to prevent automatic addition of the stable and local chart repositories. |
| Improvements | Default stable repository URL moved to a long‑term archive location; old URLs trigger a warning and can be overridden. |
| Infrastructure | Tiller container image default switched to ghcr.io/helm/tiller while still supporting the previous GCR location. |
| Bug Fixes | Multiple fixes back‑ported from Helm 3, including dependency handling, linting, and CI Docker authentication. |
| Deprecations | Stable and incubator repositories are deprecated; users are encouraged to migrate to the new archive location. |
What are the main change groups in Helm 2.17?
Repository handling changes
Helm now warns when it detects the old stable or incubator URLs and points users to the new long‑term archive location. The default repository URL is automatically set to the new location, but can be overridden with helm repo add.
Tiller image relocation
The default Tiller image has moved to ghcr.io/helm/tiller. Existing installations that rely on the previous GCR image continue to work, but new installations will pull from the GitHub Container Registry.
Init command enhancements
The helm init command now accepts --skip-refresh, letting teams skip the automatic addition of the stable and local repositories during CI/CD pipelines.
Back‑ported fixes from Helm 3
A set of stability and compatibility patches from Helm 3 were back‑ported, covering dependency caching, linting strictness, and CI Docker authentication improvements.
Miscellaneous bug fixes and clean‑ups
Various issues were resolved, including stack overflow in helm template, strict parameter handling, and test data cleanup. These changes reduce unexpected failures during chart rendering.
For detailed installation steps see the official Helm documentation.
FAQ
How do I prevent Helm 2.17 from adding the stable repo automatically?
Use the new flag: helm init --skip-refresh. This skips the default addition of the stable and local repositories.
Where is the stable repository hosted now?
The default URL points to a long‑term archive location. You can view or change it with helm repo add stable https://example.com/archive.
What image does Tiller pull by default after the upgrade?
The default image is ghcr.io/helm/tiller. Existing setups that reference the old GCR image remain functional.
Are there any breaking changes I need to be aware of?
No functional breaking changes; the main impact is the deprecation of the stable/incubator repos and the new default Tiller image. Adjust scripts that rely on the old repo URLs.
Can I still use Helm 2.17 after Helm 3 is released?
Yes, but support ends on November 13 2020. Plan to migrate to Helm 3 to stay up‑to‑date with security and feature improvements.