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/ccs-gcp-customer-procedure.adoc
+16-7Lines changed: 16 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,21 +6,30 @@
6
6
7
7
= Required customer procedure
8
8
9
-
The Customer Cloud Subscription (CCS) model allows RedHat to deploy and manage {product-title} into a customer's Google Cloud Platform (GCP) project. Red Hat requires several prerequisites to provide these services.
9
+
The Customer Cloud Subscription (CCS) model allows Red{nbsp}Hat to deploy and manage {product-title} into a customer's Google Cloud Platform (GCP) project. Red Hat requires several prerequisites to provide these services.
10
10
[NOTE]
11
11
====
12
12
The following requirements in this topic apply to {product-title} on {GCP} clusters created using both the service account and Workload Identity Federation authentication type. For additional requirements that apply to the service account authentication type only, see _Service account authentication type procedure_. For additional requirements that apply to the Workload Identity Federation authentication type only, see _Workload Identity Federation authentication type procedure_.
13
13
====
14
14
15
-
[WARNING]
16
-
====
17
-
To use {product-title} in your GCP project, the following GCP organizational policy constraints cannot be in place:
15
+
.Prerequisites
16
+
17
+
Before using {product-title} in your GCP project, confirm that the following organizational policy constraints are configured correctly where applicable:
18
18
19
-
* `constraints/iam.allowedPolicyMemberDomains` (This policy constraint is supported only if Red Hat's `DIRECTORY_CUSTOMER_IDs C02k0l5e8` and `C04j7mbwl` are included in the allow list. Use this policy constraint with caution).
19
+
* `constraints/iam.allowedPolicyMemberDomains`
20
+
** This policy constraint is supported only if Red{nbsp}Hat's Directory Customer ID's `C02k0l5e8` and `C04j7mbwl` are included in the allowlist.
* `constraints/compute.requireShieldedVm` (This policy constraint is supported only if the cluster is installed with "Enable Secure Boot support for Shielded VMs" selected during the initial cluster creation).
22
-
* `constraints/compute.vmExternalIpAccess` (This policy constraint is supported when installing a private cluster with GCP Private Service Connect (PSC). For all other cases, this policy constraint is supported only after installation).
22
+
** This policy constraint is supported only when creating a private cluster with GCP Private Service Connect (PSC). You must ensure that the `INTERNAL_TCP_UDP` load balancer type is included in the allowlist or excluded from the deny list.
23
+
+
24
+
[IMPORTANT]
23
25
====
26
+
Although the `EXTERNAL_NETWORK_TCP_UDP` load balancer type is not required when creating a private cluster with GCP Private Service Connect (PSC), disallowing it via this constraint will prevent the cluster from being able to create externally accessible load balancers.
27
+
====
28
+
29
+
* `constraints/compute.requireShieldedVm`
30
+
** This policy constraint is supported only if the cluster is created with *Enable Secure Boot support for Shielded VMs* selected during the initial cluster creation.
31
+
* `constraints/compute.vmExternalIpAccess`
32
+
** This policy constraint is supported only when creating a private cluster with GCP Private Service Connect (PSC). For all other cluster types, this policy constraint is supported only after cluster creation.
Copy file name to clipboardExpand all lines: modules/creating-a-machine-pool-cli.adoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Your Amazon EC2 Spot Instances might be interrupted at any time. Use Amazon EC2
54
54
====
55
55
endif::openshift-rosa[]
56
56
`--disk-size=<disk_size>`:: Optional: Specifies the worker node disk size. The value can be in GB, GiB, TB, or TiB. Replace `<disk_size>` with a numeric value and unit, for example `--disk-size=200GiB`.
57
-
`--availability-zone=<availability_zone_name>`::
57
+
`--availability-zone=<availability_zone_name>`::
58
58
ifdef::openshift-rosa-hcp[]
59
59
Optional: You can create a machine pool in an availability zone of your choice. Replace `<availability_zone_name>` with an availability zone name.
60
60
endif::openshift-rosa-hcp[]
@@ -196,9 +196,9 @@ I: To view all machine pools, run 'rosa list machinepools -c mycluster'
196
196
----
197
197
198
198
//ifdef::openshift-rosa-hcp[] Uncomment this out once HCP split occurs
199
-
* To add a Windows Licence Included enabled machine pool to a {hcp-title} cluster, see link:https://access.redhat.com/articles/7096903[AWS Windows License Included for ROSA with HCP].
199
+
* To add a Windows License Included enabled machine pool to a {hcp-title} cluster, see link:https://access.redhat.com/articles/7096903[AWS Windows License Included for ROSA with HCP].
200
200
+
201
-
Windows Licence Included enabled machine pools can only be created when the following criteria is met:
201
+
Windows License Included enabled machine pools can only be created when the following criteria is met:
0 commit comments