Skip to content

Commit 9bfea52

Browse files
authored
Merge pull request #52037 from skrthomas/OSDOCS-4369
OSDOCS-4369: Adding clarification about Private OpenShift cluster default behavior
2 parents b0a071d + a8c4936 commit 9bfea52

File tree

4 files changed

+20
-2
lines changed

4 files changed

+20
-2
lines changed

modules/private-clusters-about.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,10 @@
66
[id="private-clusters-about_{context}"]
77
= About private clusters
88

9-
By default, {product-title} is provisioned using publicly-accessible DNS and endpoints. You can set the DNS, Ingress Controller, and API server to private after you deploy your cluster.
9+
10+
By default, {product-title} is provisioned using publicly-accessible DNS and endpoints. You can set the DNS, Ingress Controller, and API server to private after you deploy your private cluster.
11+
12+
include::snippets/snip-private-clusters-public-ingress.adoc[]
1013

1114
[discrete]
1215
[id="private-clusters-about-dns_{context}"]

modules/private-clusters-default.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,10 @@ Public zones are not supported in Route 53 in an AWS Top Secret Region. Therefor
4545
must be private if they are deployed to an AWS Top Secret Region.
4646
====
4747
endif::aws-secret[]
48-
4948
By default, {product-title} is provisioned to use publicly-accessible DNS and endpoints. A private cluster sets the DNS, Ingress Controller, and API server to private when you deploy your cluster. This means that the cluster resources are only accessible from your internal network and are not visible to the internet.
5049

50+
include::snippets/snip-private-clusters-public-ingress.adoc[]
51+
5152
To deploy a private cluster, you must:
5253

5354
* Use existing networking that meets your requirements. Your cluster resources might be shared between other clusters on the network.

post_installation_configuration/configuring-private-cluster.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,3 +15,5 @@ include::modules/private-clusters-setting-dns-private.adoc[leveloffset=+1]
1515
include::modules/private-clusters-setting-ingress-private.adoc[leveloffset=+1]
1616

1717
include::modules/private-clusters-setting-api-private.adoc[leveloffset=+1]
18+
19+
include::modules/nw-ingresscontroller-change-internal.adoc[leveloffset=+2]
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
// Text snippet included in the following modules:
2+
//
3+
// * modules/private-clusters-default.adoc
4+
// * modules/private-clusters-about.adoc
5+
// * modules/private-clusters-about-aws.adoc
6+
7+
:_content-type: SNIPPET
8+
9+
[IMPORTANT]
10+
====
11+
If the cluster has any public subnets, load balancer services created by administrators might be publicly accessible. To ensure cluster security, verify that these services are explicitly annotated as private.
12+
====

0 commit comments

Comments
 (0)