What Is New in Helm 2.8?
| Category | Key Changes |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security / RBAC |
|
| Deprecated / Removed |
|
What Are the Main Changes in Helm 2.8?
Kubernetes 1.9 Compatibility
Helm now understands the apps/v1 workload API, selector immutability, and defaults to RollingUpdate for Deployments. This matters because you can deploy modern manifests without manual API conversion.
CLI Enhancements
New flags such as --wait for helm init, --col-width for list commands, and namespace/value support in helm lint streamline automation scripts.
Tiller Upgrade Path
The helm init --upgrade command now upgrades Tiller safely, and the added --wait flag ensures the server is ready before further actions.
Chart Metadata & Packaging
Charts can now include an appVersion field, and the packaging command gained an --app-version flag, making version tracking clearer for end‑users.
Plugin & Documentation Improvements
New plugins (k8comp, helm‑monitor) were added, and documentation was expanded to cover RBAC, TLS, and plugin installation. The helm status command now supports JSON/YAML output for easier CI consumption.
FAQ
How do I upgrade Tiller to the 2.8 version?
Run helm init --upgrade; the command now waits for Tiller to become reachable when you add the --wait flag.
Can Helm 2.8 deploy resources that use the apps/v1 API?
Yes, Helm 2.8 parses apps/v1 objects directly, so you can use the latest Deployment, StatefulSet, and DaemonSet definitions without conversion.
What does the new appVersion field provide?
It records the version of the underlying application the chart installs, separate from the chart version, helping users differentiate chart upgrades from app upgrades.
Is there a way to get structured output from helm status?
Use helm status RELEASE_NAME --output json or --output yaml to receive machine‑readable status data.
How can I ensure my CI pipeline respects the latest release when listing releases?
Helm 2.8 adds --col-width for helm list and filters to show only the most recent release per name, simplifying version checks in scripts.
For more details, see the official Helm documentation: Helm Using Guide.