restructure

Author: mletalie

_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

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 <wif_name> \ <1>
-  --project <gcp_project_id> <2>
-----
-<1> Replace `<wif_name>` with the name of your WIF configuration.
-<2> Replace `<gcp_project_id>` 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]
 ====

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].
+ 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].

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