What Is New in Helm 3.2
| Category | Key Changes |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security |
|
| Deprecated / Removed |
|
Major Change Groups in Helm 3.2
Autocompletion Overhaul
Shell completion now works for both plugins and core commands, offering dynamic suggestions and static completions. This reduces the learning curve for new users and speeds up day‑to‑day workflows.
Repository & TLS Enhancements
The new --insecure-skip-tls-verify flag lets you work with self‑signed registries without disabling TLS globally. It’s scoped to the specific repo command, keeping the rest of the client secure.
Storage Driver Evolution
A PostgreSQL driver, originally from Helm 2, is now available as a beta option. Teams that already run PostgreSQL can store release metadata there, opening a path to more robust, relational storage.
Namespace & CRD Controls
--create-namespace automatically creates the target namespace during install or upgrade, removing a common pre‑step. The --skipCRDs flag gives fine‑grained control over CRD installation when using helm upgrade --install.
Stability & Bug Fixes
Multiple regressions around rollback, delete, and update paths were fixed, and a data‑race in the client delete routine was eliminated. These changes make Helm more reliable in CI/CD pipelines.
FAQ
How do I enable insecure TLS for a single repo command?
Append --insecure-skip-tls-verify to the helm repo add, helm repo update, or helm repo remove invocation. The flag only affects that call.
Can I use the PostgreSQL storage driver in production?
It is marked as beta in 3.2, so it is suitable for testing and non‑critical environments. Expect future releases to stabilize the API before a production rollout.
What does --create-namespace change for my CI scripts?
The flag removes the need to pre‑create the namespace with kubectl create namespace. Helm will create it if it does not exist, simplifying one‑line deployments.
Why did my helm upgrade --install start installing CRDs again?
Version 3.2 introduced the --skipCRDs flag. Use it when you want to prevent Helm from re‑applying CRDs on subsequent upgrades.
Is the lookup function vulnerability still a concern for Helm 3.2?
No. The patch in 3.2 removes the flaw; only earlier 3.1.x releases were affected. Upgrading to 3.2 eliminates the risk.