Update 8.5 to 8.6
The following sections explain which adjustments must be made to migrate from Camunda 8.5.x to 8.6.x for each component.
Helm chart
Separated Ingress deprecation
The separated Ingress Helm configuration for Camunda 8 Self-Managed has been deprecated in 8.6, and will be removed from the Helm chart in 8.7. Only the combined Ingress configuration is officially supported. See the Ingress guide for more information on configuring a combined Ingress setup.
Elasticsearch nodes number
The default value of Elasticsearch deployment pods has changed from 2 to 3, and an affinity setting has been added to avoid scheduling Elasticsearch pods on the same Kubernetes worker.
Connectors
Kafka Connector supports Avro schema
The Camunda Kafka Connector supports Schema Registry as of version 8.6.0. This means:
- When using Connectors 8.6.0, you must use the following Kafka Connector versions:
- For inbound connectors: 6 (or higher)
- For outbound connector: 5 (or higher)
- When using Connectors 8.5.x (or older), you must use the following Kafka Connector versions:
- For inbound connectors: 5 (or lower)
- For outbound connector: 4 (or lower)
Avro schema support is the only breaking change for this Connector. If you do not use Avro schema, you can continue using the Connector as before.
OpenShift
We added the global.compatibility.openshift.adaptSecurityContext
variable in the values.yaml that can be used to set the following possible values:
force
: TherunAsUser
andfsGroup
values will be null in all components.disabled
: TherunAsUser
andfsGroup
values will not be modified (default).
To deploy Camunda 8 on OpenShift, run the following command:
helm install camunda camunda/camunda-platform --skip-crds \
--set global.compatibility.openshift.adaptSecurityContext=force
With this change, there is no need to do extra steps with the post-renderer. You can install the chart as normal. Please refer to the Red Hat OpenShift document for more information.