Merge pull request #86325 from mletalie/OSDOCS-12933

[OSDOCS-12933]:Update OSD on GCP docs with Mobb Feedback

Author: bergerhoffer

modules/ccs-gcp-customer-procedure.adoc

@@ -93,70 +93,4 @@ To use {product-title} in your GCP project, the following GCP organizational pol
 
 This API is required for clusters deployed with Private Service Connect.
 
-|===
-
-
-. To ensure that Red Hat can perform necessary actions, you must create an `osd-ccs-admin` IAM link:https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating_a_service_account[service account] user within the GCP project.
-
-+
-
-The following roles must be link:https://cloud.google.com/iam/docs/granting-roles-to-service-accounts#granting_access_to_a_service_account_for_a_resource[granted to the service account]:
-+
-.Required roles
-[cols="2a,3a",options="header"]
-
-|===
-
-|Role|Console role name
-
-|Compute Admin
-|`roles/compute.admin`
-
-|DNS Administrator
-|`roles/dns.admin`
-
-|Organization Policy Viewer
-|`roles/orgpolicy.policyViewer`
-
-|Service Management Administrator
-|`roles/servicemanagement.admin`
-
-|Service Usage Admin
-|`roles/serviceusage.serviceUsageAdmin`
-
-|Storage Admin
-|`roles/storage.admin`
-
-|Compute Load Balancer Admin
-|`roles/compute.loadBalancerAdmin`
-
-|Role Viewer
-|`roles/viewer`
-
-|Role Administrator
-|`roles/iam.roleAdmin`
-
-|Security Admin
-|`roles/iam.securityAdmin`
-
-|Service Account Key Admin
-|`roles/iam.serviceAccountKeyAdmin`
-
-|Service Account Admin
-|`roles/iam.serviceAccountAdmin`
-
-|Service Account User
-|`roles/iam.serviceAccountUser`
-
-|IAP-Secured Tunnel User
-|`roles/iap.tunnelResourceAccessor`^[*]^
-
-|===
-
-+
-[.small]
---
-*Required for clusters deployed with Private Service Connect.
---
-
-. link:https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating_service_account_keys[Create the service account key] for the `osd-ccs-admin` IAM service account. Export the key to a file named `osServiceAccount.json`; this JSON file will be uploaded in {cluster-manager-first} when you create your cluster.
+|===

modules/ccs-gcp-understand.adoc

@@ -11,10 +11,4 @@ Red Hat {product-title} provides a Customer Cloud Subscription (CCS) model that
 
 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 {product-title} 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. Customers have the choice of using service account keys or Workload Identity Federation when creating the roles and credentials necessary to  access Google Cloud resources within a 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.
-
-[IMPORTANT]
-====
-Unless specified, the information provided in this topic is applicable to {product-title} on {GCP} clusters that use service account keys or Workload Identity Federation (WIF) to grant the required necessary credentials.
-====
+It is recommended for the {product-title} 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. Customers have the choice of using service account keys or Workload Identity Federation when creating the roles and credentials necessary to  access Google Cloud resources within a GCP project.