Skip to content

Commit 94d869a

Browse files
authored
Merge pull request #92986 from mletalie/OSDOCS-14556
[OSDOCS-14456]Adding links to GCP docs for better user experience/fixing typos
2 parents c398d39 + 8de6fe6 commit 94d869a

File tree

2 files changed

+19
-17
lines changed

2 files changed

+19
-17
lines changed

modules/ccs-gcp-customer-requirements.adoc

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -11,34 +11,34 @@
1111
[id="ccs-gcp-requirements-account_{context}"]
1212
== Account
1313

14-
* The customer ensures that link:https://cloud.google.com/storage/quotas[Google Cloud limits] are sufficient to support {product-title} provisioned within the customer-provided GCP account.
14+
* The customer ensures that link:https://cloud.google.com/storage/quotas[Google Cloud limits] and link:https://cloud.google.com/compute/resource-usage[allocation quotas that apply to Compute Engine] are sufficient to support {product-title} provisioned within the customer-provided GCP account.
1515

1616
* The customer-provided GCP account should be in the customer's Google Cloud Organization.
1717

18-
* The customer-provided GCP account must not be transferable to Red Hat.
18+
* The customer-provided GCP account must not be transferable to Red{nbsp}Hat.
1919

20-
* The customer may not impose GCP usage restrictions on Red Hat activities. Imposing restrictions severely hinders Red Hat's ability to respond to incidents.
20+
* The customer may not impose GCP usage restrictions on Red{nbsp}Hat activities. Imposing restrictions severely hinders Red{nbsp}Hat's ability to respond to incidents.
2121

22-
* 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.
22+
* Red{nbsp}Hat deploys monitoring into GCP to alert Red{nbsp}Hat when a highly privileged account, such as a root account, logs into the customer-provided GCP account.
2323

2424
* The customer can deploy native GCP services within the same customer-provided GCP account.
2525
+
2626
[NOTE]
2727
====
28-
Customers are encouraged, but not mandated, to deploy resources in a Virtual Private Cloud (VPC) separate from the VPC hosting {product-title} and other Red Hat supported services.
28+
Customers are encouraged, but not mandated, to deploy resources in a Virtual Private Cloud (VPC) separate from the VPC hosting {product-title} and other Red{nbsp}Hat supported services.
2929
====
3030

3131
[id="ccs-gcp-requirements-access_{context}"]
3232
== Access requirements
3333

34-
* To appropriately manage the {product-title} service, Red Hat must have the `AdministratorAccess` policy applied to the administrator role at all times.
34+
* To appropriately manage the {product-title} service, Red{nbsp}Hat must have the `AdministratorAccess` policy applied to the administrator role at all times.
3535
+
3636
[NOTE]
3737
====
38-
This policy only provides Red Hat with permissions and capabilities to change resources in the customer-provided GCP account.
38+
This policy only provides Red{nbsp}Hat with permissions and capabilities to change resources in the customer-provided GCP account.
3939
====
4040

41-
* Red Hat must have GCP console access to the customer-provided GCP account. This access is protected and managed by Red Hat.
41+
* Red{nbsp}Hat must have GCP console access to the customer-provided GCP account. This access is protected and managed by Red{nbsp}Hat.
4242

4343
* The customer must not utilize the GCP account to elevate their permissions within the {product-title} cluster.
4444

@@ -47,13 +47,13 @@ This policy only provides Red Hat with permissions and capabilities to change re
4747
[id="ccs-gcp-requirements-support_{context}"]
4848
== Support requirements
4949

50-
* Red Hat recommends that the customer have at least link:https://cloud.google.com/support[Enhanced Support] from GCP.
50+
* Red{nbsp}Hat recommends that the customer have at least link:https://cloud.google.com/support[Enhanced Support] from GCP.
5151

52-
* Red Hat has authority from the customer to request GCP support on their behalf.
52+
* Red{nbsp}Hat has authority from the customer to request GCP support on their behalf.
5353

54-
* Red Hat has authority from the customer to request GCP resource limit increases on the customer-provided account.
54+
* Red{nbsp}Hat has authority from the customer to request GCP resource limit increases on the customer-provided account.
5555

56-
* Red Hat manages the restrictions, limitations, expectations, and defaults for all {product-title} clusters in the same manner, unless otherwise specified in this requirements section.
56+
* Red{nbsp}Hat manages the restrictions, limitations, expectations, and defaults for all {product-title} clusters in the same manner, unless otherwise specified in this requirements section.
5757

5858
[id="ccs-gcp-requirements-security_{context}"]
5959
== Security requirements
@@ -62,11 +62,11 @@ This policy only provides Red Hat with permissions and capabilities to change re
6262

6363
* Volume snapshots will remain within the customer-provided GCP account and customer-specified region.
6464

65-
* To manage, monitor, and troubleshoot {product-title} clusters, Red Hat must have direct access to the cluster's API server. You must not restrict or otherwise prevent Red Hat's access to the {product-title} cluster's API server.
65+
* To manage, monitor, and troubleshoot {product-title} clusters, Red{nbsp}Hat must have direct access to the cluster's API server. You must not restrict or otherwise prevent Red{nbsp}Hat's access to the {product-title} cluster's API server.
6666
+
6767
[NOTE]
6868
====
69-
SRE uses various methods to access clusters, depending on network configuration. Access to private clusters is restricted to Red Hat trusted IP addresses only. These access restrictions are managed automatically by Red Hat.
69+
SRE uses various methods to access clusters, depending on network configuration. Access to private clusters is restricted to Red{nbsp}Hat trusted IP addresses only. These access restrictions are managed automatically by Red{nbsp}Hat.
7070
====
7171
+
7272
* {product-title} requires egress access to certain endpoints over the internet. Only clusters deployed with Private Service Connect can use a firewall to control egress traffic. For additional information, see the _GCP firewall prerequisites_ section.

modules/ccs-gcp-understand.adoc

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,10 @@
77
= Understanding Customer Cloud Subscriptions on GCP
88

99

10-
Red Hat {product-title} provides a Customer Cloud Subscription (CCS) model that allows Red Hat to deploy and manage {product-title} into a customer's existing {GCP} account. Red Hat requires several prerequisites be met in order to provide this service.
10+
Red{nbsp}Hat {product-title} provides a Customer Cloud Subscription (CCS) model that allows Red{nbsp}Hat to deploy and manage {product-title} into a customer's existing {GCP} account. Red{nbsp}Hat requires several prerequisites be met in order to provide this service.
1111

12-
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.
12+
Red{nbsp}Hat recommends the usage of a 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.
1313

14-
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.
14+
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.
15+
16+
For more information about creating and managing organization resources within GCP, see link:https://cloud.google.com/resource-manager/docs/creating-managing-organization[Creating and managing organization resources].

0 commit comments

Comments
 (0)