diff --git a/docs/self-managed/concepts/multi-region/dual-region.md b/docs/self-managed/concepts/multi-region/dual-region.md
index a7035ad862a..e2500d02252 100644
--- a/docs/self-managed/concepts/multi-region/dual-region.md
+++ b/docs/self-managed/concepts/multi-region/dual-region.md
@@ -98,7 +98,6 @@ In the event of a total active region loss, the following data will be lost:
     - Zeebe **8.5+**
     - Zeebe Gateway **8.5+**
 - For the Helm chart installation method, two Kubernetes clusters are required
-  - OpenShift is not supported
 - Network
   - The regions (for example, two Kubernetes clusters) need to be able to connect to each other (for example, via VPC peering)
     - See an [example implementation](/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md) of two VPC peered Kubernetes clusters based on AWS EKS.
@@ -108,6 +107,10 @@ In the event of a total active region loss, the following data will be lost:
     - **26500** for communication to the Zeebe Gateway from client/workers
     - **26501** for the Zeebe brokers and Zeebe Gateway communication
     - **26502** for the Zeebe brokers and Zeebe Gateway communication
+  - Cluster communication
+    - Kubernetes services in one cluster must be resolvable and reachable from the other cluster and vice-versa. This is essential for proper communication and functionality across regions:
+      - For AWS EKS setups, ensure DNS chaining is configured. Refer to the [Amazon Elastic Kubernetes Service (EKS) setup guide](/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md).
+      - For OpenShift, [Submariner](https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/networking/networking#submariner) is recommended for handling multi-cluster networking. Specific implementation guides are not yet available.
 - Only specific combinations of Zeebe broker counts and replication factors are supported
   - `clusterSize` must be a multiple of **2** and a minimum of **4** to evenly distribute the brokers across the two regions.
   - `replicationFactor` must be **4** to ensure that the partitions are evenly distributed across the two regions.
diff --git a/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md b/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md
index 9189a983fba..322c6f5dd04 100644
--- a/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md
+++ b/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md
@@ -100,7 +100,6 @@ In the event of a total active region loss, the following data will be lost:
     - Zeebe **8.5+**
     - Zeebe Gateway **8.5+**
 - For the Helm chart installation method, two Kubernetes clusters are required
-  - OpenShift is not supported
 - Network
   - The regions (for example, two Kubernetes clusters) need to be able to connect to each other (for example, via VPC peering)
     - See an [example implementation](/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md) of two VPC peered Kubernetes clusters based on AWS EKS.
@@ -110,6 +109,10 @@ In the event of a total active region loss, the following data will be lost:
     - **26500** for communication to the Zeebe Gateway from client/workers
     - **26501** for the Zeebe brokers and Zeebe Gateway communication
     - **26502** for the Zeebe brokers and Zeebe Gateway communication
+  - Cluster communication:
+    - Kubernetes services in one cluster must be resolvable and reachable from the other cluster and vice-versa. This is essential for proper communication and functionality across regions:
+      - For AWS EKS setups, ensure DNS chaining is configured. Refer to the [Amazon Elastic Kubernetes Service (EKS) setup guide](/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md).
+      - For OpenShift, [Submariner](https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/networking/networking#submariner) is recommended for handling multi-cluster networking. Specific implementation guides are not yet available.
 - Only specific combinations of Zeebe broker counts and replication factors are supported
   - `clusterSize` must be a multiple of **2** and a minimum of **4** to evenly distribute the brokers across the two regions.
   - `replicationFactor` must be **4** to ensure that the partitions are evenly distributed across the two regions.