What Is New in Helm 3.8
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security |
|
| Deprecated | None for this release |
For a quick start, see the Quickstart Guide. Detailed installation steps are in the install guide.
What are the major change groups in Helm 3.8?
OCI Registry Enhancements
- OCI support is now generally available, removing the experimental flag.
- Dependencies can specify OCI charts with version ranges, just like Helm repo charts.
- Build metadata in SemVer tags is preserved; Helm converts “+” to “_” for registry storage.
helm registry loginfollows Docker CLI conventions and shares the same config file.
CLI and Search Improvements
- The new
--list-repo-urlflag quickly shows repository URLs inhelm search hub. - Release names are now validated during
helm install, preventing illegal names early.
Platform and Compatibility Updates
- Helm can be installed on Windows via Cygwin, expanding Windows developer support.
- Full compatibility with Kubernetes 1.23, aligning with the latest API versions.
Stability and Bug Fixes
- Resolved several OCI‑related panics and memory leaks.
- Improved handling of subchart CRDs when subcharts are disabled.
- General clean‑up of error messages and edge‑case handling.
FAQ
How do I reference an OCI chart with a version range?
Use the same syntax as a normal repo
dependency, e.g. version: ">=1.2.0 <2.0.0" in the Chart.yaml dependencies block.
Will my existing helm registry login commands still work?
Yes. The command now
mirrors Docker CLI behavior, and it reads the same config.json file Docker uses, so existing
credentials are reused automatically.
Can I still push charts with a “+” in the tag?
OCI registries reject “+”. Helm automatically
converts “+” to “_” when storing the tag, and reverses the conversion on pull, so the workflow remains seamless.
Do I need to change anything to support Kubernetes 1.23?
No code changes are required; Helm 3.8
includes the updated client libraries that understand the 1.23 API surface.
What should I do if I encounter a release-name validation error?
Ensure the name matches the
allowed pattern (lowercase alphanumeric and “-”). The validation now runs before any resources are created, giving
immediate feedback.