3.2.4

Latest release in branch 3.2
Released 15 Jun 2020 (5 years ago)

SoftwareHelm
Branch3.2
Status
End of life
Initial release3.2.0
22 Apr 2020 (6 years ago)
Latest patch release3.2.4
15 Jun 2020 (5 years ago)
Supported
Kubernetes versions
1.17.x - 1.14.x
Active support end11 Aug 2020 (Ended 5 years, 8 months ago)
Release noteshttps://github.com/helm/helm/releases/tag/v3.2.4
Source codehttps://github.com/helm/helm/tree/v3.2.4
Downloadhttps://github.com/helm/helm/releases/tag/v3.2.4
Helm 3.2 ReleasesView full list

What Is New in Helm 3.2

Category Key Changes
New Features
  • Added --insecure-skip-tls-verify to repository commands.
  • Beta PostgreSQL storage driver imported from Helm 2.
  • Dynamic and static plugin autocompletion improvements.
  • --create-namespace flag for helm install and helm upgrade.
  • --skipCRDs flag for helm upgrade --install.
Improvements
  • Comprehensive overhaul of shell autocompletion.
  • Updated sprig and semver libraries.
  • Clearer error messages for removed Kubernetes APIs.
  • Better handling of nil values and nested null overrides.
  • Support for multiple arguments in helm repo remove.
Bug Fixes
  • Fixed regressions in update, delete, and rollback logic.
  • Resolved a data‑race in the client delete path.
  • Corrected nil‑handling regression introduced in earlier releases.
  • Ensured chart rebuild after dependency updates during install.
  • Patched storage driver bugs for Secrets, ConfigMaps, and driver records.
  • Improved handling of invalid YAML when --debug is used.
Security
  • Patched a critical vulnerability in the lookup function (affects 3.1.x, fixed in 3.2).
  • Dependency updates address known CVEs in bundled libraries.
Deprecated / Removed
  • No major deprecations; some outdated comments were cleaned up.

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.

Releases In Branch 3.2

VersionRelease date
3.2.415 Jun 2020
(5 years ago)
3.2.022 Apr 2020
(6 years ago)