Remove redundant assembly file

eclipse-che · Sep 29, 2021 · e8be66c · e8be66c
1 parent f1ce8eb
commit e8be66c
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 24 deletions.
diff --git a/.../installation-guide/pages/configuring-communication-between-che-components.adoc b/.../installation-guide/pages/configuring-communication-between-che-components.adoc
@@ -3,4 +3,4 @@
 :keywords: installation-guide
 :page-aliases: .:configuring-communication-between-che-components, .:switching-between-external-and-internal-communication, switching-between-external-and-internal-communication
 
-include::partial$assembly_configuring-communication-between-che-components.adoc[]
+include::partial$proc_configuring-communication-between-che-components.adoc[]
diff --git a/...n-guide/partials/assembly_configuring-communication-between-che-components.adoc b/...n-guide/partials/assembly_configuring-communication-between-che-components.adoc
diff --git a/...communication-between-che-components.adoc → ...communication-between-che-components.adoc b/...communication-between-che-components.adoc → ...communication-between-che-components.adoc
@@ -1,7 +1,15 @@
-[id="using-the-operator-to-configure-communication-between-{prod-id-short}-components_{context}"]
-= Using the Operator to configure communication between {prod-short} components
+[id="configuring-communication-between-{prod-id-short}-components_{context}"]
+= Configuring communication between {prod-short} components
 
-To change between external and internal inter-component communication, update the Custom Resource.
+To communicate together, {prod-short} components use the internal services names, which are exposed in the internal {platforms-name} network.
+
+The administration can disable the use of the internal services names to force {prod-short} components to use external {platforms-ingress}. Using the external {platforms-ingress} might slow the traffic and lead to issues because it uses proxies, certificates, and firewalls.
+
+Using the external {platforms-ingress} is necessary in the following situations:
+
+* To deploy {prod-short} across multiple {platforms-name} clusters. The internal services names are not shared between distinct clusters.
+* To deploy {prod-short} across multiple namespaces. The {orch-name} NetworkPolicies restricts communication between namespaces.
+* To deploy {prod-short} with the multitenant network plugin.
 
 .Prerequisites