Last checked and updated on 04 May 2026
What Is New in Helm 3.18?
| Category | Highlights |
|---|---|
| New Features | JSON Schema 2020 support, hook annotation for error‑time logs, CPU & memory profiling flags. |
| Improvements | OCI registry fallback to HTTP, ORAS v2 upgrade, multi‑platform plugin hook support, Cobra SetOut/SetErr, env‑var preference over CLI flags. |
| Bug Fixes | mTLS proxy handling, corrected --take-ownership flag, null‑value handling in nested charts, various dependency updates. |
| Security | Dependency bumps that close known CVEs (net, containerd, distribution, etc.). |
| Deprecations | None announced for this release. |
Which new features should I start using right away?
JSON Schema 2020
Helm now validates chart values against JSON Schema 2020, giving you richer schema definitions and better error messages.
Hook output annotation
Adding helm.sh/hook-output to a hook will stream its logs to the client when the hook fails, simplifying debugging.
Profiling flags
Use --profile-cpu and --profile-mem to collect performance data without extra tooling.
What improvements make Helm 3.18 easier to operate?
- Automatic fallback to plain HTTP for OCI registries when TLS fails.
- ORAS upgraded to v2, improving OCI artifact handling.
- Multi‑platform plugin hook support enables plugins to run on different architectures.
- Cobra now uses
SetOutandSetErr, giving better control over command output. - Environment variables take precedence over command‑line flags, aligning with container best practices.
Which bugs were fixed that could affect my existing charts?
- Proxy support now works when mutual TLS is configured.
- The
--take-ownershipflag correctly respects ownership semantics. - Null values in nested global sections no longer overwrite existing objects.
- Various dependency updates resolve build and runtime issues (e.g., containerd, distribution).
How does Helm 3.18 address security concerns?
Several core libraries were bumped to versions that patch known CVEs, including net, containerd, and distribution. While Helm itself didn’t add new security features, these updates reduce the attack surface of the tooling.
FAQ
Can I use the new JSON Schema 2020 without changing my existing values files?
Yes. Existing values continue to work; the new schema is only applied when you add a values.schema.json file.
Do the profiling flags impact Helm’s normal operation?
They only collect data when the flags are present; otherwise Helm runs unchanged.
Will the OCI HTTP fallback affect secure registries?
The fallback only triggers when TLS negotiation fails, so secure registries remain protected.
How do I enable the hook‑output annotation?
Add helm.sh/hook-output: "true" to the hook’s metadata; logs appear on hook failure.
Is there any migration step required for the --take-ownership fix?
No migration is needed; the flag now behaves as documented in all future releases.