Prepare for upgrade
This guide is a starting point to get high level overview of preparation for an upgrade to Camunda 8.8 Self-Managed: assess your infrastructure, review operational changes, and choose an upgrade strategy appropriate for your environment.
Step 1: Evaluate your current setup
Check your current setup and make sure you are ready to upgrade.
| Area | Description and actions |
|---|---|
| Camunda version | Direct upgrades are only supported from 8.7.x to 8.8.x. You must upgrade all Camunda applications to it latest 8.7.x patch before upgrading to 8.8. |
| Configuration customizations | Identify non-default parameters and values in configuration files, ingress rules, external Elasticsearch/OpenSearch configurations, and custom exporters. |
Step 2: Assess Camunda 8.8 changes and impact
Review and make sure you understand the platform-level changes between Camunda 8.7 and 8.8. Understanding these highlights helps you plan your upgrade and anticipate operational impacts.
Start with the high-level overview what's new in Camunda 8.8.
| Area | What's changed | Impact |
| TBD | TDB | Low |
Step 3. Check infrastructure compatibility
Check and verify your infrastructure compatibility for Camunda 8.8.
| Area | 8.8 requirement | Action |
|---|---|---|
| Elasticsearch/OpenSearch | Elasticsearch ≥ 8.16 (OpenSearch TBD). | 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. |
You should run a load test that simulates real production traffic, as component consolidation changes resource consumption. See the sizing guidelines and benchmarking recommendations to determine appropriate cluster sizing before you upgrade your production environment.
Next steps
Once you have confirmed you are ready to upgrade and taken any actions required, proceed to the upgrade.
For more information, see the component upgrade guide and version-specific documentation.