Last checked and updated on 04 May 2026
What Is New in Helm 3.19?
| Category | Key Changes |
|---|---|
| New Features | Added httproute support to helm create for Gateway API chart scaffolding. |
| Improvements | Enhanced OCI pull handling, restored helm lint JSON‑Schema $ref support, refined k8s version parsing, and added debug logging for OCI transport. |
| Bug Fixes | Fixed regressions in helm pull, helm lint, legacy Docker login, redirect registry handling, hook deletion processing, and numerous ORAS v2 issues. |
| Security | No new security‑related changes were introduced in this release. |
| Deprecated | None. |
Which new feature stands out in Helm 3.19?
The most visible addition is the httproute template generated by helm create. It scaffolds a Gateway API HTTPRoute resource, letting developers start with a ready‑made ingress pattern.
helm create mychart
# the generated templates now include:
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
name: {{ include "mychart.fullname" . }}
spec:
rules:
- matches:
- path:
type: PathPrefix
value: /
forwardTo:
- serviceName: {{ include "mychart.fullname" . }}
port: 80
What improvements were made to OCI handling?
Helm 3.19 restores the ability to pull OCI charts when a password is supplied, fixing a regression introduced in 3.18. Debug logging for the OCI transport is now enabled, helping troubleshoot registry interactions.
- Correct use of
--usernameand--passwordwithhelm pull. - Verbose logs appear when
--debugis used.
How does Helm 3.19 address linting regressions?
The lint command now accepts JSON‑Schema $ref URLs over HTTP/HTTPS again, and it includes TLS client configuration support. This aligns lint behavior with earlier 3.17 releases.
helm lint mychart --set schemaUrl=https://example.com/schema.json
Which bugs were fixed around registry login and redirects?
Legacy Docker login now respects explicit username/password, and charts can be fetched from registries that issue HTTP redirects. The fix also prevents duplicate manifest lookups in the ORAS memory store.
- Login works with
docker://scheme. - Redirected registry URLs are followed correctly.
- ORAS v2 related crashes are resolved.
FAQ
How does the new httproute template affect my chart workflow?
The scaffold gives you a ready‑made Gateway API resource, so you can focus on business logic instead of writing the route definition from scratch.
Will helm pull work with a password again?
Yes, the command now correctly forwards the supplied credentials to the OCI registry, fixing the 3.18 regression.
What changed in helm lint regarding JSON Schema references?
References over HTTP/HTTPS are accepted again, and you can provide custom TLS settings via --set flags.
Are there any modifications to Docker legacy login handling?
Legacy login now uses the provided username and password, restoring compatibility with older registry setups.
Does the updated k8s version parsing impact compatibility checks?
The parser now mirrors upstream Kubernetes version logic, reducing false mismatches when evaluating chart kubeVersion constraints.