Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switching between external and internal ways in inter-component communication #1704

Merged
merged 4 commits into from
Dec 1, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions modules/installation-guide/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,7 @@
** xref:installing-che-using-storage-classes.adoc[]
** xref:configuring-storage-types.adoc[]
** xref:importing-tls-certificates-to-che-server-java-truststore.adoc[]
** xref:switching-between-external-and-internal-communication.adoc[]

* xref:upgrading-che.adoc[]

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
[id="switching-between-external-and-internal-communication"]
// = Configuring Labels
:navtitle: Switching between external and internal ways in inter-component communication
:keywords: installation-guide
:page-aliases: .:switching-between-external-and-internal-communication

include::partial$proc_switching-between-external-and-internal-communication.adoc[]
Original file line number Diff line number Diff line change
Expand Up @@ -34,5 +34,7 @@ The next sections describe some specific user stories.

* xref:importing-tls-certificates-to-che-server-java-truststore.adoc[]

* xref:switching-between-external-and-internal-communication.adoc[]


:context: {parent-context-of-configuring-che}
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@

[id="switching-between-external-and-internal-communication_{context}"]
= Switching between external and internal ways in inter-component communication

The communication between {prod-cli} internal components uses the internal cluster host name.
In following situations, instead, use external {platforms-ingress} in inter-component communication:

* The OpenShift instance is running multiple {prod-short} instance.
* The environment is restricting communication between namespaces.

.Prerequisites

* The `{orch-cli}` tool is available.
* An instance of {prod-short} running in {platform-name}.


.Procedure

. To use external {platforms-ingress} in inter-component communication:
+
[subs="+quotes,+attributes"]
----
$ {orch-cli} patch checluster {prod-checluster} -n {prod-namespace} --type=json -p \
'[{"op": "replace", "path": "/spec/server/useInternalClusterSVCNames", "value": false}]'
----

. To use internal cluster host name in inter-component communication:
+
[subs="+quotes,+attributes"]
----
$ {orch-cli} patch checluster {prod-checluster} -n {prod-namespace} --type=json -p \
'[{"op": "replace", "path": "/spec/server/useInternalClusterSVCNames", "value": true}]'
----