What Is New in Helm 2.15? – Summary Table
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security | No new security features; Helm 2 remains in maintenance mode with patches applied as needed. |
| Deprecated | None introduced in this release. |
What are the major change groups in Helm 2.15?
New Commands and Flags
helm test --logsstreams logs from failing test pods.helm test --maxcaps the number of concurrent test pods.helm template --api-versionslets you validate templates against a custom API version list.--outputadds JSON/YAML output to several commands for easier scripting.
Template Engine Enhancements
.Capabilities.APIVersions.Hascan now check for specific resource kinds (e.g.apps/v1/Deployment).- Improved handling of numeric values to avoid unintended float conversion.
Tiller Deployment and Compatibility
helm initnow creates a Tiller Deployment usingapps/v1, aligning with newer Kubernetes clusters.--waitbehavior expanded to include ingress host readiness and to ignore paused workloads.
Reliability and Bug Fixes
- Race condition fixed when watching pod events.
- Repo URL decoding bug resolved.
- File mode handling corrected to use proper octal values.
- Enhanced waiting logic ensures resources are fully removed before proceeding.
FAQ
How does helm test --logs improve my CI pipeline?
The flag streams the failing pod’s logs directly to the console, so you can see why a test failed without digging into the cluster manually. This reduces turnaround time when debugging CI failures.
Can I validate a chart against a newer Kubernetes API version before upgrading the cluster?
Yes. Use helm template --api-versions <list> to render the chart with the specified API versions. It helps catch deprecation warnings early.
Does the new --output flag affect existing scripts?
The flag is optional; existing scripts continue to work unchanged. When you need machine‑readable results, add --output json or --output yaml to get structured data.
What advantage does .Capabilities.APIVersions.Has give me in templates?
It lets you conditionally include resources based on the cluster’s supported API groups, avoiding runtime errors when a resource kind is unavailable.
Is the Tiller deployment change relevant for clusters already on Kubernetes 1.16+?
Absolutely. Switching to apps/v1 removes the need for legacy extensions/v1beta1 APIs, which are deprecated in newer clusters, ensuring smoother upgrades.