You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/deleting-cluster.adoc
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,3 +19,8 @@ You can delete your {product-title} cluster in {cluster-manager-first}.
19
19
. Select *Delete cluster* from the *Actions* drop-down menu.
20
20
21
21
. Type the name of the cluster highlighted in bold, then click *Delete*. Cluster deletion occurs automatically.
22
+
+
23
+
[NOTE]
24
+
====
25
+
If you delete a cluster that was installed into a GCP shared VPC, inform the Shared VPC Admin of the host project to remove the IAM policy roles granted to the service account that was referenced during cluster creation.
Copy file name to clipboardExpand all lines: modules/osd-create-cluster-ccs.adoc
+38-3Lines changed: 38 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,30 +204,58 @@ The *Use a PrivateLink* option cannot be changed after a cluster is created.
204
204
+
205
205
.. 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*.
206
206
endif::osd-on-aws[]
207
+
207
208
ifdef::osd-on-gcp[]
208
209
. Optional: To install the cluster in an existing GCP Virtual Private Cloud (VPC):
209
210
.. Select *Install into an existing VPC*.
210
211
.. 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*.
211
212
endif::osd-on-gcp[]
212
-
213
+
+
213
214
. Click *Next*.
214
215
216
+
ifdef::osd-on-gcp[]
217
+
. Optional: To install the cluster into a GCP shared VPC:
218
+
+
219
+
[IMPORTANT]
220
+
====
221
+
222
+
To install a cluster into a shared VPC, you must use {product-title} version 4.13.15 or above. Additionally, the shared VPC administrator 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].
223
+
====
224
+
225
+
.. Select *Install into GCP shared VPC*.
226
+
.. Specify the **Host project ID**. If the specified host project ID is incorrect, cluster creation fails.
227
+
+
228
+
[IMPORTANT]
229
+
====
230
+
Once you complete the steps within the cluster configuration wizard and click **Create Cluster**, the cluster will go into the "Installation Waiting" state. At this point, you must contact the Shared VPC Admin of the host project, who must assign the dynamically-generated service account the following roles: **Computer Network Administrator**, **Compute Security Administrator**, and **DNS Administrator**.
231
+
The Shared VPC Admin of the host project has 30 days to grant the listed permissions before the cluster creation fails.
232
+
For information about GCP shared VPC permissions, see link:https://cloud.google.com/vpc/docs/provisioning-shared-vpc#migs-service-accounts[Provision Shared VPC].
233
+
====
234
+
endif::osd-on-gcp[]
235
+
+
215
236
. If you opted to install the cluster in an existing
216
237
ifdef::osd-on-aws[]
217
238
AWS
218
239
endif::osd-on-aws[]
219
240
ifdef::osd-on-gcp[]
220
241
GCP
221
242
endif::osd-on-gcp[]
222
-
VPC, provide your *Virtual Private Cloud (VPC) subnet settings* and select *Next*. You must have created the Cloud network address translation (NAT) and a Cloud router. See the additional resources for information about Cloud NATs and Google VPCs.
243
+
VPC, provide your *Virtual Private Cloud (VPC) subnet settings* and select *Next*.
244
+
You must have created the Cloud network address translation (NAT) and a Cloud router. See the additional resources for information about Cloud NATs and Google VPCs.
223
245
ifdef::osd-on-aws[]
224
246
+
225
247
[NOTE]
226
248
====
227
249
You must ensure that your VPC is configured with a public and a private subnet for each availability zone that you want the cluster installed into. If you opted to use PrivateLink, only private subnets are required.
228
250
====
229
251
endif::osd-on-aws[]
230
-
252
+
ifdef::osd-on-gcp[]
253
+
+
254
+
[NOTE]
255
+
====
256
+
If you are installing a cluster into a GCP shared VPC, the VPC name and subnets are shared from the host project.
257
+
====
258
+
endif::osd-on-gcp[]
231
259
. If you opted to configure a cluster-wide proxy, provide your proxy configuration details on the *Cluster-wide proxy* page:
232
260
+
233
261
--
@@ -284,6 +312,13 @@ In the event of critical security concerns that significantly impact the securit
284
312
====
285
313
286
314
. Review the summary of your selections and click *Create cluster* to start the cluster installation. The installation takes approximately 30-40 minutes to complete.
315
+
+
316
+
ifdef::osd-on-gcp[]
317
+
[NOTE]
318
+
====
319
+
If you delete a cluster that was installed into a GCP shared VPC, inform the Shared VPC Admin of the host project to remove the IAM policy roles granted to the service account that was referenced during cluster creation.
0 commit comments