Add ingress note

camunda · Dec 13, 2024 · 3ef2228 · 3ef2228
1 parent c7a9f9b
commit 3ef2228
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/reference/announcements/870.md b/docs/reference/announcements/870.md
@@ -100,9 +100,9 @@ New migration guides will also be provided to support you when migrating from a
 Additional upgrade considerations are necessary for deployments that use custom scripts, such as Docker containers, manual installations, or custom-developed Kubernetes deployments. For these deployments, customers can either continue to deploy with their original 8.6 topology and upgrade each component independently, or adopt our Helm Chart approach for the upgrade, which allows for unifying the deployment into a single JAR or container executable.
 :::
 
-#### Separated Ingress removal
+#### Separated Ingress removed
 
-With Camunda 8.7, Helm chart supports only the Combined Ingress setup where all Camunda components run on the same Ingress object and same hostname.
+With Camunda 8.7, the Helm chart only supports combined Ingress setup, where all Camunda components run on the same Ingress object and hostname. Customers running on a separate Ingress must migrate to the combined Ingress setup, see [Ingress setup](/self-managed/setup/guides/ingress-setup.md).
 
 The following Helm chart values have been removed: