From 6de9399a13ea9761cae506ad78aaaa7d759f740d Mon Sep 17 00:00:00 2001 From: mletalie Date: Tue, 10 Dec 2024 11:01:31 -0500 Subject: [PATCH] restructure --- _topic_maps/_topic_map_osd.yml | 10 +- modules/osd-create-cluster-ccs.adoc | 48 +++---- modules/private-service-connect-create.adoc | 2 +- osd_getting_started/osd-getting-started.adoc | 6 +- ...creating-a-gcp-cluster-redhat-account.adoc | 131 ++++++++++++++++++ .../creating-a-gcp-cluster.adoc | 7 +- ...ing-a-gcp-psc-enabled-private-cluster.adoc | 1 - osd_whats_new/osd-whats-new.adoc | 2 +- 8 files changed, 167 insertions(+), 40 deletions(-) create mode 100644 osd_install_access_delete_cluster/creating-a-gcp-cluster-redhat-account.adoc diff --git a/_topic_maps/_topic_map_osd.yml b/_topic_maps/_topic_map_osd.yml index 330b5c537d..d1a042bb18 100644 --- a/_topic_maps/_topic_map_osd.yml +++ b/_topic_maps/_topic_map_osd.yml @@ -121,14 +121,16 @@ Name: Installing, accessing, and deleting OpenShift Dedicated clusters Dir: osd_install_access_delete_cluster Distros: openshift-dedicated Topics: -- Name: Creating a cluster on AWS - File: creating-an-aws-cluster -- Name: Creating a GCP Private Service Connect enabled private cluster - File: creating-a-gcp-psc-enabled-private-cluster - Name: Creating a cluster on GCP with Workload Identity Federation File: creating-a-gcp-cluster-with-workload-identity-federation +- Name: Creating a GCP Private Service Connect enabled private cluster + File: creating-a-gcp-psc-enabled-private-cluster - Name: Creating a cluster on GCP File: creating-a-gcp-cluster +#- Name: Creating a cluster on GCP with a Red Hat cloud account +# File: creating-a-gcp-cluster-redhat-account +- Name: Creating a cluster on AWS + File: creating-an-aws-cluster #- Name: Configuring your identity providers # File: config-identity-providers #- Name: Revoking privileges and access to an OpenShift Dedicated cluster diff --git a/modules/osd-create-cluster-ccs.adoc b/modules/osd-create-cluster-ccs.adoc index 3ed015de48..681a2d50c9 100644 --- a/modules/osd-create-cluster-ccs.adoc +++ b/modules/osd-create-cluster-ccs.adoc @@ -90,7 +90,11 @@ endif::osd-on-gcp[] + [NOTE] ==== -The subscription types that are available to you depend on your {product-title} subscriptions and resource quotas. For more information, contact your sales representative or Red Hat support. +The subscription types that are available to you depend on your {product-title} subscriptions and resource quotas. +ifdef::osd-on-gcp[] +Red Hat recommends deploying your cluster with the On-Demand subscription type purchased through the {GCP} Marketplace. This option provides flexible, consumption-based billing, consuming additional capacity is frictionless, and no Red Hat intervention is required. +endif::osd-on-gcp[] +For more information, contact your sales representative or Red Hat support. ==== + .. Select the *Customer Cloud Subscription* infrastructure type to deploy {product-title} in an existing cloud provider account that you own. @@ -101,11 +105,11 @@ ifdef::osd-on-aws[] endif::osd-on-aws[] ifdef::osd-on-gcp[] . Select *Run on Google Cloud Platform*. -. Select either *Service account* or *Workload Identity Federation* as the Authentication type. +. Select *Service Account* as the Authentication type. + [NOTE] ==== -For more information about authentication types, click the question icon located next to *Authentication type*. +Red Hat recommends using Workload Identity Federation as the Authentication type. For more information, see xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster-with-workload-identity-federation.adoc#osd-creating-a-cluster-on-gcp-with-workload-identity-federation[Creating a cluster on GCP with Workload Identity Federation]. ==== + endif::osd-on-gcp[] @@ -129,21 +133,8 @@ Some AWS SCPs can cause the installation to fail, even if you have the required ==== endif::osd-on-aws[] ifdef::osd-on-gcp[] -. If you selected *Service account* as the Authentication type, provide your GCP service account private key in JSON format. You can either click *Browse* to locate and attach a JSON file or add the details in the *Service account JSON* field. -. If you selected *Workload Identity Federation* as the Authentication type, you will first need to create a new WIF configuration. -Open a terminal window and run the following `ocm` CLI command. -+ -[source,terminal] ----- -$ ocm gcp create wif-config --name \ <1> - --project <2> ----- -<1> Replace `` with the name of your WIF configuration. -<2> Replace `` with the ID of the {GCP} project where the WIF configuration will be implemented. - -. Select a configured WIF configuration from the *WIF configuration* drop-down list. If you want to select the WIF configuration you created in the last step, click *Refresh* first. +. Provide your GCP service account private key in JSON format. You can either click *Browse* to locate and attach a JSON file or add the details in the *Service account JSON* field. endif::osd-on-gcp[] - . Click *Next* to validate your cloud provider account and go to the *Cluster details* page. . On the *Cluster details* page, provide a name for your cluster and specify the cluster details: @@ -154,9 +145,9 @@ To customize the subdomain, select the *Create customize domain prefix* checkbox .. Select a cluster version from the *Version* drop-down menu. ifdef::osd-on-gcp[] + -[NOTE] +[IMPORTANT] ==== -Workload Identity Federation (WIF) is only supported on {product-title} version 4.17 and later. +Clusters configured with Private Service Connect (PSC) are only supported on OpenShift Dedicated version 4.17 and later. For more information regarding PSC, see _Private Service Overview_ in the _Additional resources_ section. ==== + endif::osd-on-gcp[] @@ -187,7 +178,7 @@ The key is used for encrypting all control plane, infrastructure, worker node ro + endif::osd-on-aws[] ifdef::osd-on-gcp[] -... Select *Use Custom KMS keys* to use custom KMS keys. If you prefer not to use custom KMS keys, leave the default setting *Use default KMS Keys*. +... Select *Use custom KMS keys* to use custom KMS keys. If you prefer not to use custom KMS keys, leave the default setting *Use default KMS Keys*. + [IMPORTANT] ==== @@ -213,18 +204,23 @@ If *Enable FIPS cryptography* is selected, *Enable additional etcd encryption* i + [NOTE] ==== -By enabling etcd encryption for the key values in etcd, you will incur a performance overhead of approximately 20%. The overhead is a result of introducing this second layer of encryption, in addition to the default control plane storage encryption that encrypts the etcd volumes. Consider enabling etcd encryption only if you specifically require it for your use case. +By enabling additional etcd encryption, you will incur a performance overhead of approximately 20%. The overhead is a result of introducing this second layer of encryption, in addition to the default control plane storage encryption that encrypts the etcd volumes. Consider enabling etcd encryption only if you specifically require it for your use case. ==== + .. Click *Next*. -. On the *Default machine pool* page, select a *Compute node instance type* and a *Compute node count*. The number and types of nodes that are available depend on your {product-title} subscription. If you are using multiple availability zones, the compute node count is per zone. +. On the *Default machine pool* page, select a *Compute node instance type* from the drop-down menu. +. Optional: Select the *Enable autoscaling* checkbox to enable autoscaling. +.. Click *Edit cluster autoscaling settings* to make changes to the autoscaling settings. +.. Once you have made your desired changes, click *Close*. +.. Select a minimum and maximum node count. Node counts can be selected by engaging the available plus and minus signs or inputting the desired node count into the number input field. +. Select a *Compute node count* from the drop-down menu. + [NOTE] ==== -After your cluster is created, you can change the number of compute nodes in your cluster, but you cannot change the compute node instance type in a machine pool. The number and types of nodes available to you depend on your {product-title} subscription. +If you are using multiple availability zones, the compute node count is per zone. After your cluster is created, you can change the number of compute nodes in your cluster, but you cannot change the compute node instance type in a machine pool. The number and types of nodes available to you depend on your {product-title} subscription. ==== - ++ ifdef::osd-on-aws[] . Choose your preference for the Instance Metadata Service (IMDS) type, either using both IMDSv1 and IMDSv2 types or requiring your EC2 instances to use only IMDSv2. You can access instance metadata from a running instance in two ways: + @@ -244,7 +240,7 @@ IMDSv2 uses session-oriented requests. With session-oriented requests, you creat For more information regarding IMDS, see link:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html[Instance metadata and user data] in the AWS documentation. endif::osd-on-aws[] -. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*. +. Optional: Expand *Add node labels* to add labels to your nodes. Click *Add additional label* to add an additional node label and select *Next*. ifdef::osd-on-gcp[] + [IMPORTANT] @@ -255,7 +251,7 @@ This step refers to labels within Kubernetes, not Google Cloud. For more informa endif::osd-on-gcp[] . On the *Network configuration* page, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster. ifdef::osd-on-gcp[] -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. +If you select *Private* and selected {product-title} version 4.17 or later as your cluster version, *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. + [NOTE] ==== diff --git a/modules/private-service-connect-create.adoc b/modules/private-service-connect-create.adoc index dfc275d8e2..665392dc88 100644 --- a/modules/private-service-connect-create.adoc +++ b/modules/private-service-connect-create.adoc @@ -7,4 +7,4 @@ = Creating a private cluster with Private Service Connect Private Service Connect is supported with the Customer Cloud Subscription (CCS) infrastructure type only. To create an {product-title} on {GCP} using PSC, see - xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-cluster-gcp-account_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with Google Cloud Marketplace]. \ No newline at end of file + xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-gcp-cluster-ccs_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with CCS]. \ No newline at end of file diff --git a/osd_getting_started/osd-getting-started.adoc b/osd_getting_started/osd-getting-started.adoc index 375f32e9e4..cffd57f4fa 100644 --- a/osd_getting_started/osd-getting-started.adoc +++ b/osd_getting_started/osd-getting-started.adoc @@ -35,11 +35,7 @@ Complete the steps in one of the following sections to deploy {product-title} in *** An {product-title} cluster deployed on {GCP} can be created in Private cluster mode, without any cloud resources. In this configuration, Red Hat uses Google Cloud Private Service Connect (PSC) to manage and monitor a cluster to avoid all public ingress network traffic. For more details, see xref:../osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.adoc[Creating a GCP Private Service Connect enabled private cluster]. -** For installing and interacting with the {product-title} cluster deployed on the {GCP} using the Service Account authentication type, see following topics: - -*** *xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-cluster-gcp-account_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with Google Cloud Marketplace]*: You can install {product-title} in your own {GCP} account with Google Cloud Marketplace. - -*** *xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-cluster-rhm-gcp-account_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with Red Hat Marketplace]*: You can install {product-title} in your own {GCP} account with Red Hat Marketplace. +** For installing and interacting with the {product-title} cluster deployed on the {GCP} using the Service Account authentication type, see xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-gcp-cluster-ccs_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP]. [id="osd-getting-started-create-cluster-red-hat-cloud-account"] === Creating a cluster using a Red Hat cloud account diff --git a/osd_install_access_delete_cluster/creating-a-gcp-cluster-redhat-account.adoc b/osd_install_access_delete_cluster/creating-a-gcp-cluster-redhat-account.adoc new file mode 100644 index 0000000000..bbea79c28c --- /dev/null +++ b/osd_install_access_delete_cluster/creating-a-gcp-cluster-redhat-account.adoc @@ -0,0 +1,131 @@ +:_mod-docs-content-type: ASSEMBLY +[id="osd-creating-a-gcp-cluster-rh-account"] += Creating a cluster on GCP with a Red Hat cloud account +include::_attributes/attributes-openshift-dedicated.adoc[] +:context: osd-creating-a-gcp-cluster-rh-account + +toc::[] + +:_mod-docs-content-type: PROCEDURE + +Through {cluster-manager-url}, you can create an {product-title} cluster on {GCP} using a standard cloud provider account owned by Red Hat. + +.Procedure + +. Log in to {cluster-manager-url} and click *Create cluster*. + +. In the *Cloud* tab, click *Create cluster* in the *Red Hat OpenShift Dedicated* row. + +. Under *Billing model*, configure the subscription type and infrastructure type: +.. Select the *Annual* subscription type. Only the *Annual* subscription type is available when you deploy a cluster using a Red Hat cloud account. ++ +For information about {product-title} subscription options, see link:https://access.redhat.com/documentation/en-us/openshift_cluster_manager/1-latest/html-single/managing_clusters/index#assembly-cluster-subscriptions[Cluster subscriptions and registration] in the {cluster-manager} documentation. ++ +[NOTE] +==== +You must have the required resource quota for the *Annual* subscription type to be available. For more information, contact your sales representative or Red Hat support. +==== ++ +.. Select the *Red Hat cloud account* infrastructure type to deploy {product-title} in a cloud provider account that is owned by Red Hat. +.. Click *Next*. + + +. Select *Run on Google Cloud Platform* + +and click *Next*. + +. On the *Cluster details* page, provide a name for your cluster and specify the cluster details: +.. Add a *Cluster name*. +.. Optional: Cluster creation generates a domain prefix as a subdomain for your provisioned cluster on `openshiftapps.com`. If the cluster name is less than or equal to 15 characters, that name is used for the domain prefix. If the cluster name is longer than 15 characters, the domain prefix is randomly generated as a 15-character string. ++ +To customize the subdomain, select the *Create custom domain prefix* checkbox, and enter your domain prefix name in the *Domain prefix* field. The domain prefix cannot be longer than 15 characters, must be unique within your organization, and cannot be changed after cluster creation. +.. Select a cluster version from the *Version* drop-down menu. +.. Select a cloud provider region from the *Region* drop-down menu. +.. Select a *Single zone* or *Multi-zone* configuration. +.. Select a *Persistent storage* capacity for the cluster. For more information, see the _Storage_ section in the {product-title} service definition. +.. Specify the number of *Load balancers* that you require for your cluster. For more information, see the _Load balancers_ section in the {product-title} service definition. ++ + +.. Optional: Select *Enable Secure Boot for Shielded VMs* to use Shielded VMs when installing your cluster. For more information, see link:https://cloud.google.com/security/products/shielded-vm[Shielded VMs]. ++ +[IMPORTANT] +==== +To successfully create a cluster, you must select *Enable Secure Boot support for Shielded VMs* if your organization has the policy constraint `constraints/compute.requireShieldedVm` enabled. For more information regarding GCP organizational policy constraints, see link:https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints[Organization policy constraints]. +==== ++ + +.. Leave *Enable user workload monitoring* selected to monitor your own projects in isolation from Red Hat Site Reliability Engineer (SRE) platform metrics. This option is enabled by default. + +. Optional: Expand *Advanced Encryption* to make changes to encryption settings. ++ +.. Optional: Select *Enable FIPS cryptography* if you require your cluster to be FIPS validated. ++ +[NOTE] +==== +If *Enable FIPS cryptography* is selected, *Enable additional etcd encryption* is enabled by default and cannot be disabled. You can select *Enable additional etcd encryption* without selecting *Enable FIPS cryptography*. +==== + +.. Optional: Select *Enable additional etcd encryption* if you require etcd key value encryption. With this option, the etcd key values are encrypted, but not the keys. This option is in addition to the control plane storage encryption that encrypts the etcd volumes in {product-title} clusters by default. ++ +[NOTE] +==== +By enabling etcd encryption for the key values in etcd, you will incur a performance overhead of approximately 20%. The overhead is a result of introducing this second layer of encryption, in addition to the default control plane storage encryption that encrypts the etcd volumes. Consider enabling etcd encryption only if you specifically require it for your use case. +==== ++ +.. Click *Next*. + +. On the *Default machine pool* page, select a *Compute node instance type* and a *Compute node count*. The number and types of nodes that are available depend on your {product-title} subscription. If you are using multiple availability zones, the compute node count is per zone. ++ +[NOTE] +==== +After your cluster is created, you can change the number of compute nodes, but you cannot change the compute node instance type in a machine pool. For clusters that use the CCS model, you can add machine pools after installation that use a different instance type. The number and types of nodes available to you depend on your {product-title} subscription. +==== + +. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*. + +. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster. + +. Click *Next*. + +. In the *CIDR ranges* dialog, configure custom classless inter-domain routing (CIDR) ranges or use the defaults that are provided. ++ +[IMPORTANT] +==== +CIDR configurations cannot be changed later. Confirm your selections with your network administrator before proceeding. + +If the cluster privacy is set to *Private*, you cannot access your cluster until you configure private connections in your cloud provider. +==== + +. On the *Cluster update strategy* page, configure your update preferences: +.. Choose a cluster update method: +** Select *Individual updates* if you want to schedule each update individually. This is the default option. +** Select *Recurring updates* to update your cluster on your preferred day and start time, when updates are available. ++ +[NOTE] +==== +You can review the end-of-life dates in the update lifecycle documentation for {product-title}. For more information, see link:https://access.redhat.com/documentation/en-us/openshift_dedicated/4/html/introduction_to_openshift_dedicated/policies-and-service-definition#osd-life-cycle[OpenShift Dedicated update life cycle]. +==== ++ +.. Provide administrator approval based on your cluster update method: +** Individual updates: If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*. +** Recurring updates: If you selected recurring updates for your cluster, provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment. ++ +.. If you opted for recurring updates, select a preferred day of the week and upgrade start time in UTC from the drop-down menus. +.. Optional: You can set a grace period for *Node draining* during cluster upgrades. A *1 hour* grace period is set by default. +.. Click *Next*. ++ +[NOTE] +==== +In the event of critical security concerns that significantly impact the security or stability of a cluster, Red Hat Site Reliability Engineering (SRE) might schedule automatic updates to the latest z-stream version that is not impacted. The updates are applied within 48 hours after customer notifications are provided. For a description of the critical impact security rating, see link:https://access.redhat.com/security/updates/classification[Understanding Red Hat security ratings]. +==== + +. Review the summary of your selections and click *Create cluster* to start the cluster installation. The installation takes approximately 30-40 minutes to complete. ++ +. Optional: On the *Overview* tab, you can enable the delete protection feature by selecting *Enable*, which is located directly under *Delete Protection: Disabled*. This will prevent your cluster from being deleted. To disable delete protection, select *Disable*. +By default, clusters are created with the delete protection feature disabled. ++ + +.Verification + +* You can monitor the progress of the installation in the *Overview* page for your cluster. You can view the installation logs on the same page. Your cluster is ready when the *Status* in the *Details* section of the page is listed as *Ready*. + diff --git a/osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc b/osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc index 0211625f2a..0dae9eb9e8 100644 --- a/osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc +++ b/osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc @@ -21,12 +21,15 @@ You can install {product-title} on {GCP} by using your own GCP account through t * You reviewed the xref:../osd_getting_started/osd-understanding-your-cloud-deployment-options.adoc#osd-understanding-your-cloud-deployment-options[{product-title} cloud deployment options]. include::modules/osd-create-cluster-ccs.adoc[leveloffset=+1] -include::modules/osd-create-cluster-gcp-account.adoc[leveloffset=+1] +//include::modules/osd-create-cluster-gcp-account.adoc[leveloffset=+1] include::modules/osd-create-cluster-red-hat-account.adoc[leveloffset=+1] -include::modules/osd-create-cluster-rhm-gcp-account.adoc[leveloffset=+1] +//include::modules/osd-create-cluster-rhm-gcp-account.adoc[leveloffset=+1] [id="additional-resources_{context}"] == Additional resources +* For information about Workload Identity Federation, see xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster-with-workload-identity-federation.adoc#osd-creating-a-cluster-on-gcp-with-workload-identity-federation[Creating a cluster on GCP with Workload Identity Federation]. + +* For information about Private Service Connect (PSC), see xref:../osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.adoc#private-service-connect-overview_osd-creating-a-gcp-psc-enabled-private-cluster[Private Service Connect overview]. * For information about configuring a proxy with {product-title}, see xref:../networking/configuring-cluster-wide-proxy.adoc#configuring-a-cluster-wide-proxy[Configuring a cluster-wide proxy]. * For information about persistent storage for {product-title}, see the xref:../osd_architecture/osd_policy/osd-service-definition.adoc#sdpolicy-storage_osd-service-definition[Storage] section in the {product-title} service definition. * For information about load balancers for {product-title}, see the xref:../osd_architecture/osd_policy/osd-service-definition.adoc#load-balancers_osd-service-definition[Load balancers] section in the {product-title} service definition. diff --git a/osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.adoc b/osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.adoc index 5bd7b6e3b3..7f8a2aa0f5 100644 --- a/osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.adoc +++ b/osd_install_access_delete_cluster/creating-a-gcp-psc-enabled-private-cluster.adoc @@ -19,4 +19,3 @@ include::modules/private-service-connect-create.adoc[leveloffset=+1] For information on {product-title} on {GCP} cluster prerequisites, see xref:../osd_planning/gcp-ccs.adoc#ccs-gcp-customer-requirements_gcp-ccs[Customer Requirements]. For information about configuring your firewalls , see xref:../osd_planning/gcp-ccs.adoc#osd-gcp-psc-firewall-prerequisites_gcp-ccs[GCP firewall prerequisites]. -//Once https://issues.redhat.com/browse/OSDOCS-7329 goes live, put link directly to this topic. \ No newline at end of file diff --git a/osd_whats_new/osd-whats-new.adoc b/osd_whats_new/osd-whats-new.adoc index 0436139db9..88a268aac1 100644 --- a/osd_whats_new/osd-whats-new.adoc +++ b/osd_whats_new/osd-whats-new.adoc @@ -76,7 +76,7 @@ For more information about region availabilities, see xref:../osd_architecture/o * **Cluster install update.** {product-title} clusters can now be installed on {GCP} shared VPCs. For more information, see xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-gcp-cluster-ccs_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with CCS]. -* **{product-title} on Google Cloud Marketplace availability.** When creating an {product-title} (OSD) cluster on Google Cloud through the Hybrid Cloud Console, customers can now select Google Cloud Marketplace as their preferred billing model. This billing model allows Red Hat customers to take advantage of their link:https://cloud.google.com/docs/cuds[Google Committed Use Discounts (CUD)] towards {product-title} purchased through the Google Cloud Marketplace. For more information, see xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-cluster-gcp-account_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with Google Cloud Marketplace]. +* **{product-title} on Google Cloud Marketplace availability.** When creating an {product-title} (OSD) cluster on Google Cloud through the Hybrid Cloud Console, customers can now select Google Cloud Marketplace as their preferred billing model. This billing model allows Red Hat customers to take advantage of their link:https://cloud.google.com/docs/cuds[Google Committed Use Discounts (CUD)] towards {product-title} purchased through the Google Cloud Marketplace. For more information, see xref:../osd_install_access_delete_cluster/creating-a-gcp-cluster.adoc#osd-create-gcp-cluster-ccs_osd-creating-a-cluster-on-gcp[Creating a cluster on GCP with CCS]. [id="osd-known-issues_{context}"] == Known issues