Este contenido no está disponible en el idioma seleccionado.
Chapter 3. Customer Cloud Subscriptions on GCP
OpenShift Dedicated provides a Customer Cloud Subscription (CCS) model that allows Red Hat to deploy and manage clusters in a customer’s existing Google Cloud Platform (GCP) account.
3.1. Understanding Customer Cloud Subscriptions on GCP
Red Hat OpenShift Dedicated provides a Customer Cloud Subscription (CCS) model that allows Red Hat to deploy and manage OpenShift Dedicated into a customer’s existing Google Cloud Platform (GCP) account. Red Hat requires several prerequisites be met in order to provide this service.
Red Hat recommends the usage of GCP project, managed by the customer, to organize all of your GCP resources. A project consists of a set of users and APIs, as well as billing, authentication, and monitoring settings for those APIs.
It is recommended for the OpenShift Dedicated cluster using a CCS model to be hosted in a GCP project within a GCP organization. The Organization resource is the root node of the GCP resource hierarchy and all resources that belong to an organization are grouped under the organization node. An IAM service account with certain roles granted is created and applied to the GCP project. When you make calls to the API, you typically provide service account keys for authentication. Each service account is owned by a specific project, but service accounts can be provided roles to access resources for other projects.
3.2. Customer requirements
OpenShift Dedicated clusters using a Customer Cloud Subscription (CCS) model on Google Cloud Platform (GCP) must meet several prerequisites before they can be deployed.
3.2.1. Account
- The customer ensures that Google Cloud limits are sufficient to support OpenShift Dedicated provisioned within the customer-provided GCP account.
- The customer-provided GCP account should be in the customer’s Google Cloud Organization with the applicable Service Account applied.
- The customer-provided GCP account must not be transferable to Red Hat.
- The customer may not impose GCP usage restrictions on Red Hat activities. Imposing restrictions severely hinders Red Hat’s ability to respond to incidents.
- Red Hat deploys monitoring into GCP to alert Red Hat when a highly privileged account, such as a root account, logs into the customer-provided GCP account.
The customer can deploy native GCP services within the same customer-provided GCP account.
NoteCustomers are encouraged, but not mandated, to deploy resources in a Virtual Private Cloud (VPC) separate from the VPC hosting OpenShift Dedicated and other Red Hat supported services.
3.2.2. Access requirements
To appropriately manage the OpenShift Dedicated service, Red Hat must have the
AdministratorAccesspolicy applied to the administrator role at all times.NoteThis policy only provides Red Hat with permissions and capabilities to change resources in the customer-provided GCP account.
- Red Hat must have GCP console access to the customer-provided GCP account. This access is protected and managed by Red Hat.
- The customer must not utilize the GCP account to elevate their permissions within the OpenShift Dedicated cluster.
- Actions available in the OpenShift Cluster Manager must not be directly performed in the customer-provided GCP account.
3.2.3. Support requirements
- Red Hat recommends that the customer have at least Enhanced Support from GCP.
- Red Hat has authority from the customer to request GCP support on their behalf.
- Red Hat has authority from the customer to request GCP resource limit increases on the customer-provided account.
- Red Hat manages the restrictions, limitations, expectations, and defaults for all OpenShift Dedicated clusters in the same manner, unless otherwise specified in this requirements section.
3.2.4. Security requirements
- The customer-provided IAM credentials must be unique to the customer-provided GCP account and must not be stored anywhere in the customer-provided GCP account.
- Volume snapshots will remain within the customer-provided GCP account and customer-specified region.
Red Hat must have ingress access to the API server through allowlist IP addresses.
NoteFor information about allowlist IP addresses, see Additional resources.
- Red Hat must have egress allowed to forward system and audit logs to a Red Hat managed central logging stack.
3.3. Required customer procedure
The Customer Cloud Subscription (CCS) model allows Red Hat to deploy and manage OpenShift Dedicated into a customer’s Google Cloud Platform (GCP) project. Red Hat requires several prerequisites to provide these services.
To use OpenShift Dedicated in your GCP project, the following GCP organizational policy constraints cannot be in place:
-
constraints/iam.allowedPolicyMemberDomains(This policy constraint is supported only if Red Hat’sDIRECTORY_CUSTOMER_ID C02k0l5e8is included in the allow list. Use this policy constraint with caution). -
constraints/compute.restrictLoadBalancerCreationForTypes -
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). -
constraints/compute.vmExternalIpAccess(This policy constraint is supported only after installation).
Procedure
- Create a Google Cloud project to host the OpenShift Dedicated cluster.
Enable the following required APIs in the project that hosts your OpenShift Dedicated cluster:
Table 3.1. Required API services API service Console service name deploymentmanager.googleapis.comcompute.googleapis.comcloudapis.googleapis.comcloudresourcemanager.googleapis.comdns.googleapis.comnetworksecurity.googleapis.comiamcredentials.googleapis.comiam.googleapis.comservicemanagement.googleapis.comserviceusage.googleapis.comstorage-api.googleapis.comstorage-component.googleapis.comorgpolicy.googleapis.comTo ensure that Red Hat can perform necessary actions, you must create an
osd-ccs-adminIAM service account user within the GCP project.The following roles must be granted to the service account:
Table 3.2. Required roles Role Console role name Compute Admin
roles/compute.adminDNS Administrator
roles/dns.adminOrganization Policy Viewer
roles/orgpolicy.policyViewerService Management Administrator
roles/servicemanagement.adminService Usage Admin
roles/serviceusage.serviceUsageAdminStorage Admin
roles/storage.adminCompute Load Balancer Admin
roles/compute.loadBalancerAdminRole Viewer
roles/viewerRole Administrator
roles/iam.roleAdminSecurity Admin
roles/iam.securityAdminService Account Key Admin
roles/iam.serviceAccountKeyAdminService Account Admin
roles/iam.serviceAccountAdminService Account User
roles/iam.serviceAccountUser-
Create the service account key for the
osd-ccs-adminIAM service account. Export the key to a file namedosServiceAccount.json; this JSON file will be uploaded in Red Hat OpenShift Cluster Manager when you create your cluster.
3.4. Red Hat managed Google Cloud resources
Red Hat is responsible for creating and managing the following IAM Google Cloud Platform (GCP) resources.
3.4.1. IAM service account and roles
The osd-managed-admin IAM service account is created immediately after taking control of the customer-provided GCP account. This is the user that will perform the OpenShift Dedicated cluster installation.
The following roles are attached to the service account:
| Role | Console role name | Description |
|---|---|---|
| Compute Admin |
| Provides full control of all Compute Engine resources. |
| DNS Administrator |
| Provides read-write access to all Cloud DNS resources. |
| Security Admin |
| Security admin role, with permissions to get and set any IAM policy. |
| Storage Admin |
| Grants full control of objects and buckets. When applied to an individual bucket, control applies only to the specified bucket and objects within the bucket. |
| Service Account Admin |
| Create and manage service accounts. |
| Service Account Key Admin |
| Create and manage (and rotate) service account keys. |
| Service Account User |
| Run operations as the service account. |
| Role Administrator |
| Provides access to all custom roles in the project. |
3.4.2. IAM group and roles
The sd-sre-platform-gcp-access Google group is granted access to the GCP project to allow Red Hat Site Reliability Engineering (SRE) access to the console for emergency troubleshooting purposes.
The following roles are attached to the group:
| Role | Console role name | Description |
|---|---|---|
| Compute Admin |
| Provides full control of all Compute Engine resources. |
| Editor |
| Provides all viewer permissions, plus permissions for actions that modify state. |
| Organization Policy Viewer |
| Provides access to view Organization Policies on resources. |
| Project IAM Admin |
| Provides permissions to administer IAM policies on projects. |
| Quota Administrator |
| Provides access to administer service quotas. |
| Role Administrator |
| Provides access to all custom roles in the project. |
| Service Account Admin |
| Create and manage service accounts. |
| Service Usage Admin |
| Ability to enable, disable, and inspect service states, inspect operations, and consume quota and billing for a consumer project. |
| Tech Support Editor |
| Provides full read-write access to technical support cases. |
3.5. Provisioned GCP Infrastructure
This is an overview of the provisioned Google Cloud Platform (GCP) components on a deployed OpenShift Dedicated cluster. For a more detailed listing of all provisioned GCP components, see the OpenShift Container Platform documentation.
3.5.1. Compute instances
GCP compute instances are required to deploy the control plane and data plane functions of OpenShift Dedicated in GCP. Instance types might vary for control plane and infrastructure nodes depending on worker node count.
Single availability zone
- 2 infra nodes (custom machine type: 4 vCPU and 32 GB RAM)
- 3 control plane nodes (custom machine type: 8 vCPU and 32 GB RAM)
- 2 worker nodes (custom machine type: 4 vCPU and 16 GB RAM)
Multiple availability zones
- 3 infra nodes (custom machine type: 4 vCPU and 32 GB RAM)
- 3 control plane nodes (custom machine type: 8 vCPU and 32 GB RAM)
- 3 worker nodes (custom machine type: 4 vCPU and 16 GB RAM)
3.5.2. Storage
Infrastructure volumes:
- 300 GB SSD persistent disk (deleted on instance deletion)
- 110 GB Standard persistent disk (kept on instance deletion)
Worker volumes:
- 300 GB SSD persistent disk (deleted on instance deletion)
Control plane volumes:
- 350 GB SSD persistent disk (deleted on instance deletion)
3.5.3. VPC
- Subnets: One master subnet for the control plane workloads and one worker subnet for all others.
- Router tables: One global route table per VPC.
- Internet gateways: One internet gateway per cluster.
- NAT gateways: One master NAT gateway and one worker NAT gateway per cluster.
3.5.4. Services
The following services must be enabled on a GCP CCS cluster:
-
deploymentmanager -
compute -
cloudapis -
cloudresourcemanager -
dns -
iamcredentials -
iam -
servicemanagement -
serviceusage -
storage-api -
storage-component -
orgpolicy -
networksecurity
3.6. GCP account limits
The OpenShift Dedicated cluster uses a number of Google Cloud Platform (GCP) components, but the default quotas do not affect your ability to install an OpenShift Dedicated cluster.
A standard OpenShift Dedicated cluster uses the following resources. Note that some resources are required only during the bootstrap process and are removed after the cluster deploys.
| Service | Component | Location | Total resources required | Resources removed after bootstrap |
|---|---|---|---|---|
| Service account | IAM | Global | 5 | 0 |
| Firewall Rules | Compute | Global | 11 | 1 |
| Forwarding Rules | Compute | Global | 2 | 0 |
| In-use global IP addresses | Compute | Global | 4 | 1 |
| Health checks | Compute | Global | 3 | 0 |
| Images | Compute | Global | 1 | 0 |
| Networks | Compute | Global | 2 | 0 |
| Static IP addresses | Compute | Region | 4 | 1 |
| Routers | Compute | Global | 1 | 0 |
| Routes | Compute | Global | 2 | 0 |
| Subnetworks | Compute | Global | 2 | 0 |
| Target Pools | Compute | Global | 3 | 0 |
| CPUs | Compute | Region | 28 | 4 |
| Persistent Disk SSD (GB) | Compute | Region | 896 | 128 |
If any of the quotas are insufficient during installation, the installation program displays an error that states both which quota was exceeded and the region.
Be sure to consider your actual cluster size, planned cluster growth, and any usage from other clusters that are associated with your account. The CPU, Static IP addresses, and Persistent Disk SSD (Storage) quotas are the ones that are most likely to be insufficient.
If you plan to deploy your cluster in one of the following regions, you will exceed the maximum storage quota and are likely to exceed the CPU quota limit:
- asia-east2
- asia-northeast2
- asia-south1
- australia-southeast1
- europe-north1
- europe-west2
- europe-west3
- europe-west6
- northamerica-northeast1
- southamerica-east1
- us-west2
You can increase resource quotas from the GCP console, but you might need to file a support ticket. Be sure to plan your cluster size early so that you can allow time to resolve the support ticket before you install your OpenShift Dedicated cluster.
