Prepare for upgrade
This page is a work in progress for Camunda 8.9 and will be updated as upgrade requirements are finalized.
Prepare your Self-Managed environment for an upgrade to Camunda 8.9. Use this guide to confirm that your deployment is eligible for upgrade and to complete any actions required before running the upgrade.
Evaluate your current environment
Before upgrading, verify that your current installation meets the minimum requirements.
| Area | What to check |
|---|---|
| Camunda version | Direct upgrades to 8.9 are supported only from the latest 8.8.x patch. If you are running an earlier version, first upgrade to 8.8. See Upgrading from an earlier version. |
| Environment support | Ensure your platform and dependencies are supported in 8.9. See Supported environments. |
| Customizations | Identify non-default values in Helm values, application YAML files, Ingress configuration, exporters, and Elasticsearch/OpenSearch setup. |
Review required pre-upgrade actions for Camunda 8.9
This section lists any actions you must complete before upgrading to Camunda 8.9.
| Area | What's changed/Action required | Impact |
For a complete list of changes, see What’s new in Camunda 8.9.
Verify infrastructure compatibility
Review your infrastructure to confirm compatibility with Camunda 8.9.
| Area | 8.8 requirement | Action |
|---|---|---|
| Elasticsearch/OpenSearch | Elasticsearch 8.16+, OpenSearch 2.17+. | Upgrade the cluster to the new version. Check the supported environments matrix to confirm the minimum version. |
| CPU/Memory | Consolidated Zeebe StatefulSet shares limits. | Measure current usage. Test with a load generator. |
| Storage | Same or higher IOPS as 8.7. | Check there is required space for temporary migration file. |
Component consolidation in 8.8 changes resource consumption patterns. Before upgrading production, run a load test that simulates real traffic and validate CPU, memory, and storage behavior.
Next steps
Once you have confirmed upgrade eligibility and completed any required preparation steps, proceed with the upgrade method that matches your deployment:
For more information on component-specific changes, see the component upgrade guide and version-specific documentation.