Camunda has supported Helm 3 across recent releases and documented Helm 4 behavior, workarounds, and compatibility details along the way. With Helm 3 now approaching the end of life, that approach needs to change. Helm 3 bug fixes are supported until July 8, 2026, and security fixes until November 11, 2026. The official Helm v3 support announcement explains this transition window in more detail. After the November date, Helm 3 will no longer receive upstream maintenance. Starting with Camunda 8.10, our Helm charts will officially be supported only with Helm 4. Helm 3 will no longer be supported for installing or upgrading Camunda 8 from 8.10 onward, and Camunda 8.9 is the last minor release that supports Helm 3.
Camunda version and Helm chart version
Since Camunda 8.4, the Helm chart is versioned independently from the application. Use the following table to find the chart version that corresponds to your Camunda release, or check the full version matrix for the complete list.
| Camunda Version | Helm Chart Version |
|---|---|
| Camunda 8.7 | 12.x |
| Camunda 8.8 | 13.x |
| Camunda 8.9 | 14.x |
| Camunda 8.10 | 15.x |
Camunda 8.9—the transition release
Camunda 8.9, using Helm chart 14.x, is the only chart line that supports both Helm 3 and Helm 4. If you are currently running Camunda 8.7, 8.8, or 8.9 with Helm 3, you do not need to move immediately on the day 8.10 is released. However, Camunda 8.9 should be your landing point on Helm 3 and your validation point for moving to Helm 4.
Camunda 8.10 and later—Helm 4 only
Starting with Camunda 8.10, Helm 3 will no longer be supported. For chart 15.x and later, Camunda will treat Helm 4 as the supported baseline and drop Helm 3 from the official test matrix.
What this means for existing deployments
If your platform teams still use Helm 3 in clusters or CI/CD pipelines, the practical takeaway is straightforward: Camunda 8.9 is your last minor release on Helm 3. Before moving to Camunda 8.10+, you must migrate your Helm workflows to Helm 4. The Camunda Helm 4 migration guide walks you through what changed and how to migrate safely.
What to do next
For teams preparing for Camunda 8.10, we recommend the following steps:
- Check which Helm CLI version is currently used in your local workflows, automation, and production delivery pipelines.
- If you are still on Helm 3, plan the migration while running on Camunda 8.9.
- Review the Helm 4 migration guide so your teams understand which Camunda and chart versions map to which Helm versions.
- Validate your installation and upgrade flows with Helm 4 in a non-production environment before adopting Camunda 8.10 in production.
- Update CI pipelines so that Helm 4 is the standard CLI for Camunda 8.10 and later.
Why we are making this change
This change aligns with Camunda’s broader breaking-change strategy: when an upstream dependency reaches end of life, we remove support once there has been clear notice and a documented migration path. In practice, this change helps avoid a situation where customers unknowingly run unsupported combinations like Camunda 8.10 with Helm 3.
Looking ahead
With Camunda 8.10, Helm 4 becomes the supported standard for Self-Managed Helm installations. This gives customers a clear rule, gives support teams a more consistent answer, and helps Camunda invest in quality for a single modern Helm toolchain. If you are already on Helm 4, no action is needed beyond following the usual upgrade guidance. If you have any questions, feel free to reach out to your support team or CSM.
