Last checked and updated on 04 May 2026
What Is New in Helm 3.5
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security |
|
| Deprecated | None announced in this release |
Key Changes in Helm 3.5
Expanded Template Function Library
Helm now bundles over twenty new functions from the Sprig library (v3.2.0). These helpers simplify string manipulation, date handling, and data conversion directly inside chart templates. In practice, you can replace custom shell scripts with concise {{ .Values | toJson }} style expressions.
OCI Registry Support for Charts
The oci:// scheme lets you pull charts from OCI‑compatible registries and declare them in Chart.yaml dependencies. The feature is gated behind an experiment flag, so enable it with HELM_EXPERIMENTAL_OCI=1. This matters because it aligns Helm with the broader container ecosystem and removes the need for a separate chart repository.
Dependency Build Refresh Control
The new --skip-refresh option on helm dep build skips the remote index refresh step. Use it when you know the local requirements.lock is up‑to‑date, which speeds up CI pipelines.
Job‑Aware Waiting
Pairing --wait-for-jobs with --wait forces Helm to block until all Job resources finish successfully. This is useful for migrations or batch jobs that must complete before the release is considered stable.
Custom Kubernetes CA File
The --kube-cafile flag and HELM_KUBECAFILE environment variable let you point Helm at a specific CA bundle, overriding the system default. This is handy in air‑gapped clusters where the API server uses a private certificate authority.
Stability and Bug Fixes
Numerous bugs were squashed: OCI dependency builds now work reliably, flag handling for TLS certificates is corrected, and chart loading no longer panics on unexpected file sequences. These fixes improve the day‑to‑day developer experience and reduce flaky test runs.
For a quick start with the new features, see the Helm Quickstart Guide and the Installation Guide.
FAQ
How do I enable OCI support in Helm 3.5?
Set the environment variable HELM_EXPERIMENTAL_OCI=1 before running any Helm command that references an oci:// repository.
Can I use helm dep build without contacting the chart repo?
Yes, add the --skip-refresh flag to skip the remote index lookup; this works when your lock file already reflects the desired versions.
What does --wait-for-jobs actually wait for?
It blocks until all Job resources created by the release reach a Complete status, then Helm reports success.
Is there a way to point Helm at a custom CA without editing kubeconfig?
Use the --kube-cafile flag or set HELM_KUBECAFILE to the path of your CA bundle.
Do the new template functions require any additional configuration?
No, they are bundled with Helm 3.5; you can start using them in any chart template immediately.