docs(self-managed): Helm chart Elasticsearch nodes number changed (#4255

) Signed-off-by: Ahmed AbouZaid <[email protected]> Co-authored-by: Cole Garbo <[email protected]>
camunda · Sep 5, 2024 · 4952122 · 4952122
1 parent 845166a
commit 4952122
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 2 deletions.
diff --git a/docs/reference/announcements.md b/docs/reference/announcements.md
@@ -115,10 +115,16 @@ The `CorrelationResult` record has been changed compared to the previous version
 
 An example of how to use the new `CorrelationResult` can be found in the [Connector SDK documentation](/components/connectors/custom-built-connectors/connector-sdk.md#inbound-connector-runtime-logic).
 
-### Separated Ingress deprecation warning
+### Camunda 8 Self-Managed
+
+#### 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](/self-managed/setup/guides/ingress-setup.md) for more information on configuring a combined Ingress setup.
 
+#### Helm chart - 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.
+
 ## Camunda 8.5
 
 Release date: 9th of April 2024

diff --git a/docs/self-managed/operational-guides/update-guide/850-to-860.md b/docs/self-managed/operational-guides/update-guide/850-to-860.md
@@ -6,4 +6,12 @@ description: "Review which adjustments must be made to migrate from Camunda 8.5.
 
 The following sections explain which adjustments must be made to migrate from Camunda 8.5.x to 8.6.x for each component.
 
-TBD
+## 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](/self-managed/setup/guides/ingress-setup.md) 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.