Last checked and updated on 04 May 2026
What Is New in Helm 2.2?
| Category | Key Additions |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security |
|
| Deprecated | None for this release |
Which major areas were changed in Helm 2.2?
Chart testing
Helm now ships with a helm test command that runs hooks defined in a chart. This gives developers a fast way to verify a release behaves as expected before promoting it.
Third‑Party Resources (TPR)
Helm can create and upgrade TPR objects, allowing custom API extensions to be managed alongside native resources.
Repository authentication
Beyond basic auth, Helm clients can present TLS certificates when pulling charts, tightening supply‑chain security.
Release lifecycle flags
The new --wait flag blocks until all resources become ready, and helm list --namespace narrows results to a specific namespace.
Dependency handling
Charts can reference local directories in requirements.yaml, and the condition/tag system lets umbrella charts enable or disable sub‑charts dynamically.
Template enhancements
Additional built‑in objects (.Release.*, .Capabilities) and the fromYAML function expand what can be expressed in templates.
FAQ
How do I run tests for a newly deployed chart?
Use helm test <release-name>. Helm will execute any test-success or test-failure hooks defined in the chart and report the results.
Can I upgrade a Third‑Party Resource with Helm?
Yes. Helm 2.2 adds create and upgrade support for TPRs, so you can manage custom API objects the same way you manage Deployments or Services.
What do I need to do to use TLS when pulling charts from a private repo?
Place the client certificate and key files in the chart repository definition (under certFile and keyFile) and Helm will use them during fetch operations.
When should I use the --wait flag?
Apply it to helm install or helm upgrade when you need the command to return only after all pods, services, and other resources report a ready state.
How can I conditionally enable a sub‑chart?
Add a tag or condition entry in requirements.yaml and reference it in the parent chart’s values; Helm will include the sub‑chart only when the condition evaluates to true.