What’s new in Helm 3.20?
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security | No new security‑related changes were introduced in this release. |
| Deprecated | None. |
For a quick start, see the Helm Quickstart Guide. Detailed upgrade steps are in the Installation Guide.
Which major changes should I pay attention to in Helm 3.20?
SDK & language runtime upgrades
The SDK now aligns with Kubernetes API v0.35.0, which means charts can reference newer API objects without additional patches. The Go 1.25 runtime brings performance improvements and better module handling.
CLI enhancements
The new --timeout option on repo commands prevents hangs when a remote chart repository is slow or unresponsive. Replacing NewSimpleClientset removes a deprecation warning and prepares the code for future client‑set changes.
Stability fixes
Uninstall with --keep-history now correctly suspends prior releases, which matters for audit trails. Rollback logic now relies on errors.Is, eliminating false‑positive matches. Several nil‑pointer panics and merge issues have been squashed, making the CLI more reliable in CI pipelines.
FAQ
Can I upgrade from Helm 3.19 to 3.20 without reinstalling?
Yes. A simple helm version check confirms the binary, then run helm repo update to refresh indexes. No chart migration is required.
Do the new SDK API versions affect existing charts?
Existing charts continue to work; the bump only expands the set of supported API versions. If you start using newer Kubernetes resources, the SDK will now generate the correct manifests.
What does the --timeout flag change for helm repo add?
It caps the HTTP request duration. If the remote repository does not respond within the specified period, Helm aborts the operation, preventing indefinite hangs.
Is the helm uninstall --keep-history bug fix safe for production?
The fix ensures the previous release state is marked as superseded rather than left active. This preserves history while keeping the cluster clean, which is safe for production use.
Do I need to rebuild my custom plugins after the Go upgrade?
Plugins compiled against the old Go version should still run, but rebuilding with Go 1.25 is recommended to benefit from the latest compiler optimizations and avoid potential ABI mismatches.