For the complete documentation index, see llms.txt.
Skip to main content
Version: 8.10 (unreleased)

Upgrade Helm chart

Upgrade a Camunda 8 Self-Managed deployment installation using the official Camunda Helm charts.

earlier versions

If you are upgrading from a version earlier than 8.8, see upgrading from an earlier version.

Upgrading to Camunda 8.10

Camunda 8.10 (chart 15.x) requires the Helm CLI v4. Switch to the Helm v4 CLI before you run helm upgrade. No release-state migration is required. See Move from the Helm v3 CLI to v4.

Upgrade guides​

Use the following guides to upgrade a Camunda 8 Self-Managed deployment installation using the official Camunda Helm charts.

Upgrade Camunda 8.8 to 8.9 using Helm icon

Upgrade Camunda 8.8 to 8.9 using Helm

Follow the main Helm upgrade guide to perform the required configuration changes and run the Helm upgrade.

Patch upgrades within the same minor version

For patch upgrades within the same minor version, such as 8.8.9 to 8.8.23, there is no separate upgrade guide unless a specific patch's release notes specify additional required actions. Use the Helm chart version matrix to identify the chart version for your target Camunda patch version, and review the relevant patch release notes before upgrading.

Helm chart version​

The Camunda Helm chart version is independent from the Camunda application version. Use the Helm chart version matrix to identify the Helm chart version that deploys your Camunda application version.

You can also list available chart versions using the Helm CLI:

helm repo update
helm search repo camunda/camunda-platform --versions

Upgrade notes​

Bitnami Docker repository migration​

On August 28, 2025, Bitnami migrated its container images from bitnami to bitnamilegacy. The Camunda Helm charts have been updated to use the new repository.

If you are still using a Camunda Helm chart that references the old repository, use the Helm chart Bitnami legacy values file to override the image repositories.

See the Bitnami GitHub announcement for details.

Web Modeler persistence PVC name​

In some 8.10 chart versions, the Web Modeler restapi deployment referenced a persistent volume claim named <release>-webModeler-data (camelCase), which did not match the chart-managed PVC <release>-webmodeler-data (lowercase). This name mismatch prevented the Web Modeler persistence volume from mounting. A patched 8.10 chart corrects the claimName so the restapi pod mounts the existing <release>-webmodeler-data PVC.

No action is required for most deployments. The fix only corrects the deployment's claim reference; it does not rename the PVC. On upgrade, the restapi pod mounts the already-existing <release>-webmodeler-data PVC and no data migration is needed. The persisted volume holds only /tmp scratch and cache data — Web Modeler content is stored in PostgreSQL.

If you manually created a <release>-webModeler-data (capital M) PVC as a workaround for the broken mount, the restapi pod stops using it after you upgrade to a patched chart. The manual PVC is not deleted; it remains orphaned and continues to consume storage until you act. Choose one of the following:

  • Set webModeler.persistence.existingClaim to your manually created PVC to keep using it, or
  • Delete the orphaned PVC after confirming the restapi pod successfully mounts <release>-webmodeler-data.