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

Prepare for upgrade

Prepare your Self-Managed environment for an upgrade to Camunda 8.10.

About

Use this guide to confirm upgrade eligibility, understand platform-level changes, and identify actions you may need to take before running an upgrade.

All Camunda upgrades must follow the required upgrade procedure: upgrade to the latest patch of your current minor first, then upgrade one minor version at a time without skipping minors. Skipping a minor version fails the schema compatibility check and blocks startup. Upgrading to the latest patch of each minor is strongly recommended for fix coverage, but the check itself compares minor versions.

See version compatibility checks and supported upgrade paths.

Evaluate your current environment

Before upgrading, verify that your current installation meets the minimum requirements.

AreaWhat to check
Camunda versionDirect upgrades to 8.10 are supported from 8.9.x. If you are running an earlier version, first upgrade to 8.9. Upgrading to the latest available 8.9.x patch first is strongly recommended for fix coverage. See upgrading from an earlier version.
Environment supportEnsure your platform and dependencies are supported in 8.10. See supported environments.
CustomizationsIdentify non-default values in Helm values, application YAML files, Ingress configuration, exporters, and secondary storage setup (for example, Elasticsearch/OpenSearch or RDBMS).

Verify infrastructure compatibility

Review your infrastructure to confirm compatibility with Camunda 8.10.

Area8.10 requirementAction
Secondary storage (Elasticsearch/OpenSearch)Elasticsearch 8.19+, OpenSearch 2.19+. Elasticsearch 9.2+ and OpenSearch 3.4+ now supported.Upgrade the cluster to the minimum version. Check the supported environments matrix to confirm compatibility.
Secondary storage (RDBMS)Supported vendor and version required for your selected component set.Check the RDBMS support policy and confirm any component-specific limitations before upgrading.
CPU/MemorySame consolidated Orchestration StatefulSet as 8.9.No new requirements compared to 8.9.
StorageSame or higher IOPS as 8.9.No change from 8.9.

Next steps

Once you have confirmed upgrade eligibility and completed any required preparation steps, proceed with the upgrade method that matches your deployment:

tip

For more information on component-specific changes, see the component upgrade guide and version-specific documentation.