Last checked and updated on 04 May 2026
What Is New in Helm 1.2?
| Category | Key Changes |
|---|---|
| New Features | Chart repository support, helm serve for local repos, helm dep dependency manager, helm lint, helm template, client‑only helm init |
| Improvements | Faster chart packaging, richer error messages, multi‑values file handling, stricter name validation |
| Bug Fixes | Resolved fetch race condition, corrected repo URL parsing, fixed install rollback edge case |
| Security | SHA256 checksum verification for downloaded charts, optional GPG signature verification |
| Deprecated | helm fetch --untar flag, helm install without an explicit release name |
For a deeper dive, see the official Helm 1.2 documentation.
How did Helm 1.2 enhance chart repository handling?
- Introduced first‑class support for remote chart repositories via
helm repo addandhelm repo update. - Added
helm serve, a lightweight HTTP server that turns a local directory into a repository, useful for CI pipelines. - Implemented SHA256 checksum verification for each chart download, reducing the chance of corrupted artifacts.
What new dependency management capabilities arrived in Helm 1.2?
- The
helm depcommand lets you define, fetch, and update chart dependencies inrequirements.yaml. - Dependencies are now packaged as sub‑charts, enabling version pinning and transitive dependency resolution.
- Automatic pruning of unused dependencies during
helm dep updatekeeps the chart bundle lean.
Which templating and linting tools were added in this release?
helm lintvalidates chart structure, required fields, and common pitfalls before installation.helm templaterenders chart templates locally, allowing developers to preview Kubernetes manifests without a cluster.- Template functions received minor enhancements, such as
defaultand improved handling of nil values.
What security‑related features were introduced?
- Every chart fetched from a repository now includes a SHA256 checksum file; Helm verifies the checksum automatically.
- Optional GPG signature verification can be enabled with
--verify, providing cryptographic assurance of chart provenance. - Improved handling of insecure HTTP URLs – Helm now warns users and prefers HTTPS when available.
Which CLI behaviours changed or were deprecated?
helm init --client-onlyallows developers to set up only the client side, useful for environments without Tiller.- The
helm fetch --untarflag is deprecated; users should runhelm fetchfollowed byhelm templateor manual extraction. - Providing an explicit release name to
helm installis now mandatory; Helm will no longer generate a random name.
FAQ
Can I use Helm 1.2 without a Tiller server?
Yes, the new helm init --client-only flag sets up the client locally, allowing chart rendering and linting without a Tiller instance.
How do I verify a chart’s integrity after adding a repository?
Helm automatically checks the SHA256 checksum file that ships with each chart; you can also enable GPG verification with --verify during helm fetch.
What is the recommended way to manage sub‑charts now?
Define them in requirements.yaml and run helm dep update – Helm will fetch the correct versions and embed them as sub‑charts.
Is helm serve suitable for production use?
It is designed for development and CI scenarios; for production you should host a proper HTTP server or object storage bucket that serves the repository index.
What happens if I run helm install without a name?
Helm 1.2 will reject the command and prompt you to supply a release name, aligning the CLI with the upcoming Helm 2 behavior.