Skip to content

Commit 29e570d

Browse files
mletaliemletalie
committed
PSC UI
1 parent 9a78a41 commit 29e570d

File tree

3 files changed

+91
-16
lines changed

3 files changed

+91
-16
lines changed

‎modules/osd-create-cluster-ccs.adoc

Lines changed: 31 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -220,12 +220,20 @@ endif::osd-on-aws[]
220220
. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*.
221221

222222
. On the *Network configuration* page, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.
223+
ifdef::osd-on-gcp[]
224+
If you select *Private*, *Use Private Service Connect* is selected by default. Private Service Connect (PSC) is Google Cloud’s security-enhanced networking feature. You can disable PSC by clicking the *Use Private Service Connect* checkbox.
225+
+
226+
[NOTE]
227+
====
228+
Red Hat recommends using Private Service Connect when deploying a private {product-title} cluster on Google Cloud. Private Service Connect ensures there is a secured, private connectivity between Red Hat infrastructure, Site Reliability Engineering (SRE) and private {product-title} clusters.
229+
====
230+
endif::osd-on-gcp[]
223231
+
224232
[IMPORTANT]
225233
====
226234
If you are using private API endpoints, you cannot access your cluster until you update the network settings in your cloud provider account.
227235
====
228-
236+
+
229237
ifdef::osd-on-aws[]
230238
. Optional: To install the cluster in an existing AWS Virtual Private Cloud (VPC):
231239
.. Select *Install into an existing VPC*.
@@ -242,7 +250,28 @@ endif::osd-on-aws[]
242250
ifdef::osd-on-gcp[]
243251
. Optional: To install the cluster in an existing GCP Virtual Private Cloud (VPC):
244252
.. Select *Install into an existing VPC*.
253+
+
254+
[IMPORTANT]
255+
====
256+
Private Service Connect is supported only with *Install into an existing VPC*.
257+
====
258+
+
245259
.. If you are installing into an existing VPC and you want to enable an HTTP or HTTPS proxy for your cluster, select *Configure a cluster-wide proxy*.
260+
+
261+
[IMPORTANT]
262+
====
263+
In order to configure a cluster-wide proxy for your cluster, you must first create the Cloud network address translation (NAT) and a Cloud router. See the _Additional resources_ section for more information.
264+
====
265+
+
266+
. Accept the default application ingress settings, or to create your own custom settings, select *Custom Settings*.
267+
268+
.. Optional: Provide route selector.
269+
.. Optional: Provide excluded namespaces.
270+
.. Select a namespace ownership policy.
271+
.. Select a wildcard policy.
272+
+
273+
For more information about custom application ingress settings, click on the information icon provided for each setting.
274+
246275
endif::osd-on-gcp[]
247276
+
248277
. Click *Next*.
@@ -253,7 +282,7 @@ ifdef::osd-on-gcp[]
253282
[IMPORTANT]
254283
====
255284

256-
To install a cluster into a Shared VPC, you must use {product-title} version 4.13.15 or above. Additionally, the VPC owner of the host project must enable a project as a host project in their Google Cloud console. For more information, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#set-up-shared-vpc[Enable a host project].
285+
To install a cluster into a Shared VPC, you must use {product-title} version 4.13.15 or later. Additionally, the VPC owner of the host project must enable a project as a host project in their Google Cloud console. For more information, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#set-up-shared-vpc[Enable a host project].
257286
====
258287

259288
.. Select *Install into GCP Shared VPC*.

‎modules/osd-create-cluster-gcp-account.adoc

Lines changed: 27 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -90,22 +90,46 @@ After your cluster is created, you can change the number of compute nodes, but y
9090

9191
. Click *Next*.
9292

93-
. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.
93+
. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster. If you select *Private*, *Use Private Service Connect* is selected by default. Private Service Connect (PSC) is Google Cloud’s security-enhanced networking feature. You can disable PSC by clicking the *Use Private Service Connect* checkbox.
94+
+
95+
[NOTE]
96+
====
97+
Red Hat recommends using Private Service Connect when deploying a private {product-title} cluster on Google Cloud. Private Service Connect ensures there is a secured, private connectivity between Red Hat infrastructure, Site Reliability Engineering (SRE) and private {product-title} clusters.
98+
====
99+
//Once PSC docs are live add link from note above.
94100
+
95101
. Optional: To install the cluster in an existing GCP Virtual Private Cloud (VPC):
96102
.. Select *Install into an existing VPC*.
103+
+
104+
[IMPORTANT]
105+
====
106+
Private Service Connect is supported only with *Install into an existing VPC*.
107+
====
108+
+
97109
.. If you are installing into an existing VPC and you want to enable an HTTP or HTTPS proxy for your cluster, select *Configure a cluster-wide proxy*.
110+
+
111+
[IMPORTANT]
112+
====
113+
In order to configure a cluster-wide proxy for your cluster, you must first create the Cloud network address translation (NAT) and a Cloud router. See the _Additional resources_ section for more information.
114+
====
115+
+
116+
. Accept the default application ingress settings, or to create your own custom settings, select *Custom Settings*.
98117

118+
.. Optional: Provide route selector.
119+
.. Optional: Provide excluded namespaces.
120+
.. Select a namespace ownership policy.
121+
.. Select a wildcard policy.
99122
+
123+
For more information about custom application ingress settings, click on the information icon provided for each setting.
124+
100125
. Click *Next*.
101-
+
102126

103127
. Optional: To install the cluster into a GCP Shared VPC:
104128
+
105129
[IMPORTANT]
106130
====
107131

108-
To install a cluster into a Shared VPC, you must use {product-title} version 4.13.15 or above. Additionally, the VPC owner of the host project must enable a project as a host project in their Google Cloud console. For more information, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#set-up-shared-vpc[Enable a host project].
132+
To install a cluster into a Shared VPC, you must use {product-title} version 4.13.15 or later. Additionally, the VPC owner of the host project must enable a project as a host project in their Google Cloud console. For more information, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#set-up-shared-vpc[Enable a host project].
109133
====
110134

111135
.. Select *Install into GCP Shared VPC*.
@@ -119,8 +143,6 @@ For information about Shared VPC permissions, see link:https://cloud.google.com/
119143
====
120144
+
121145
. If you opted to install the cluster in an existing GCP VPC, provide your *Virtual Private Cloud (VPC) subnet settings* and select *Next*.
122-
You must have created the Cloud network address translation (NAT) and a Cloud router. See the "Additional resources" section for information about Cloud NATs and Google VPCs.
123-
124146
+
125147
[NOTE]
126148
====

‎modules/osd-create-cluster-rhm-gcp-account.adoc

Lines changed: 33 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -90,22 +90,45 @@ After your cluster is created, you can change the number of compute nodes, but y
9090

9191
. Click *Next*.
9292

93-
. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.
93+
. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster. If you select *Private*, *Use Private Service Connect* is selected by default. Private Service Connect (PSC) is Google Cloud’s security-enhanced networking feature. You can disable PSC by clicking the *Use Private Service Connect* checkbox.
94+
+
95+
[NOTE]
96+
====
97+
Red Hat recommends using Private Service Connect when deploying a private {product-title} cluster on Google Cloud. Private Service Connect ensures there is a secured, private connectivity between Red Hat infrastructure, Site Reliability Engineering (SRE) and private {product-title} clusters.
98+
====
99+
//Once PSC docs are live add link from note above.
94100
+
95101
. Optional: To install the cluster in an existing GCP Virtual Private Cloud (VPC):
96102
.. Select *Install into an existing VPC*.
103+
+
104+
[IMPORTANT]
105+
====
106+
Private Service Connect is supported only with *Install into an existing VPC*.
107+
====
108+
+
97109
.. If you are installing into an existing VPC and you want to enable an HTTP or HTTPS proxy for your cluster, select *Configure a cluster-wide proxy*.
110+
+
111+
[IMPORTANT]
112+
====
113+
In order to configure a cluster-wide proxy for your cluster, you must first create the Cloud network address translation (NAT) and a Cloud router. See the _Additional resources_ section for more information.
114+
====
115+
+
116+
. Accept the default application ingress settings, or to create your own custom settings, select *Custom Settings*.
98117

118+
.. Optional: Provide route selector.
119+
.. Optional: Provide excluded namespaces.
120+
.. Select a namespace ownership policy.
121+
.. Select a wildcard policy.
99122
+
123+
For more information about custom application ingress settings, click on the information icon provided for each setting.
124+
100125
. Click *Next*.
101-
+
102126

103-
. Optional: To install the cluster into a GCP Shared VPC:
127+
. Optional: To install the cluster into a GCP shared VPC:
104128
+
105129
[IMPORTANT]
106130
====
107-
108-
To install a cluster into a Shared VPC, you must use {product-title} version 4.13.15 or above. Additionally, the VPC owner of the host project must enable a project as a host project in their Google Cloud console. For more information, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#set-up-shared-vpc[Enable a host project].
131+
To install a cluster into a GCP shared VPC, you must use {product-title} version 4.13.15 or later. Additionally, the VPC owner of the host project must enable a project as a host project in their Google Cloud console. For more information, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#set-up-shared-vpc[Enable a host project].
109132
====
110133

111134
.. Select *Install into GCP Shared VPC*.
@@ -118,17 +141,18 @@ The VPC owner of the host project has 30 days to grant the listed permissions be
118141
For information about Shared VPC permissions, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#migs-service-accounts[Provision Shared VPC].
119142
====
120143
+
121-
. If you opted to install the cluster in an existing GCP VPC, provide your *Virtual Private Cloud (VPC) subnet settings* and select *Next*.
122-
You must have created the Cloud network address translation (NAT) and a Cloud router. See the "Additional resources" section for information about Cloud NATs and Google VPCs.
144+
. If you opted to install the cluster into an existing VPC, provide your *Virtual Private Cloud (VPC) subnet settings* and select *Next*.
123145
+
146+
124147
[NOTE]
125148
====
126-
If you are installing a cluster into a Shared VPC, the VPC name and subnets are shared from the host project.
149+
If you are installing a cluster into a GCP Shared VPC, the VPC name and subnets are shared from the host project.
127150
====
128151
+
152+
129153
. Click *Next*.
130154
. If you opted to configure a cluster-wide proxy, provide your proxy configuration details on the *Cluster-wide proxy* page:
131-
+
155+
132156
.. Enter a value in at least one of the following fields:
133157
** Specify a valid *HTTP proxy URL*.
134158
** Specify a valid *HTTPS proxy URL*.

0 commit comments

Comments
 (0)