Move from the Helm v3 CLI to v4
Camunda 8.9 (chart 14.x) supports both Helm CLI v3 and v4.
Camunda recommends Helm CLI v4 and supports it for the full Camunda 8.9 release cycle. Camunda supports Helm CLI v3 (3.10 or later) until February 10, 2027, when upstream support ends. After February 10, 2027, Camunda no longer supports Helm CLI v3. Customers who continue to use Helm CLI v3 after that date do so at their own risk.
Switching CLIs does not require a release-state migration.
Why no migration is required
Helm is a client-side tool. The CLI renders chart templates and applies the resulting manifests to the cluster. Helm release metadata is stored as Kubernetes Secrets in the release namespace, and Helm CLI v3 and v4 read and write the same release-storage format.
This means:
- The same release works under both CLIs against the same cluster.
- There is no
helm 3to4step for Camunda charts. - You do not need to reinstall, re-import, or back up and restore release state when you change CLI versions.
Switch from Helm CLI v3 to v4
-
Install the Helm CLI v4 on the workstation that runs your Helm commands. See Installing Helm.
-
Verify the CLI version:
helm versionConfirm the output reports a
v4.xclient version. -
Verify the existing release is visible to the new CLI:
helm list -n <namespace>Your existing Camunda release appears with the same name, chart version, and revision history.
-
Continue with your normal
helm upgradeworkflow. See Upgrade Helm chart.
Helm CLI v4 behavior changes to review
Helm CLI v4 enables server-side apply by default and removes some Helm CLI v3 plugin behaviors. Review these changes before your first install or upgrade with Helm CLI v4:
Helm CLI v3 support
- Chart 14.x supports Helm CLI v3 and v4. With Helm CLI v3, the chart shows a warning when you run
helm installorhelm upgrade. See Camunda Helm chart compatibility. - Helm CLI v3.22.0 is the final Helm CLI v3 minor release. See the Helm v3 end-of-life announcement.