You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/osd-create-cluster-gcp-account.adoc
+80-5Lines changed: 80 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,17 +13,92 @@ Through OpenShift Cluster Manager Hybrid Cloud Console, you can create an OpenSh
13
13
14
14
. In the *Cloud* tab, click *Create cluster* in the *Red Hat OpenShift Dedicated* row.
15
15
16
-
. Under *Billing* model, configure the subscription type and infrastructure type:
16
+
. Under *Billing model*, configure the subscription type and infrastructure type:
17
17
.. Select the *On-Demand* subscription type.
18
18
.. From the dropdown menu, select *Google Cloud Marketplace*.
19
19
.. Select the *Customer Cloud Subscription* infrastructure type to deploy OpenShift Dedicated in a cloud provider account that is owned by Google.
20
20
.. Click *Next*.
21
-
. Under *Cloud provider*, read the provided prerequisites and the Google terms and conditions. Add your service account key.
21
+
. Under *Cluster Settings > Cloud provider*, read the provided prerequisites and the Google terms and conditions. Add your service account key.
22
22
.. Click *Review Google Terms and Agreements".
23
23
.. After reviewing the Google terms and agreements, check the *Google terms and agreements* box.
24
-
..Add your service account key
24
+
.. Add your service account key
25
+
+
25
26
[NOTE]
26
27
====
27
-
For more information about service account keys, click the information icon located next to *Service account key*
28
+
For more information about service account keys, click the information icon located next to *Service account key*.
28
29
====
29
-
..Click *Next*.
30
+
.. Click *Next*.
31
+
. On the *Cluster Settings > Cluster details* page, provide a name for your cluster and specify the cluster details:
32
+
.. Add a *Cluster name*.
33
+
.. Select a cluster version from the *Version* drop-down menu.
34
+
.. Select a cloud provider region from the *Region* drop-down menu.
35
+
.. Select a *Single zone* or *Multi-zone* configuration.
36
+
.. Select a *Persistent storage* capacity for the cluster. For more information, see the _Storage_ section in the {product-title} service definition.
37
+
.. 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.
38
+
.. 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.
39
+
.. 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.
40
+
+
41
+
[NOTE]
42
+
====
43
+
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.
44
+
====
45
+
.. Click *Next*.
46
+
47
+
. On the *Cluster Settings > 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.
48
+
+
49
+
[NOTE]
50
+
====
51
+
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.
52
+
====
53
+
54
+
. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*.
55
+
56
+
. In the *Cluster privacy* dialog, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.
57
+
58
+
. Click *Next*.
59
+
60
+
. In the *CIDR ranges* dialog, configure custom classless inter-domain routing (CIDR) ranges or use the defaults that are provided.
61
+
+
62
+
[IMPORTANT]
63
+
====
64
+
CIDR configurations cannot be changed later. Confirm your selections with your network administrator before proceeding.
65
+
66
+
If the cluster privacy is set to *Private*, you cannot access your cluster until you configure private connections in your cloud provider.
67
+
====
68
+
69
+
. On the *Cluster update strategy* page, configure your update preferences:
70
+
.. Choose a cluster update method:
71
+
** Select *Individual updates* if you want to schedule each update individually. This is the default option.
72
+
** Select *Recurring updates* to update your cluster on your preferred day and start time, when updates are available.
73
+
+
74
+
[NOTE]
75
+
====
76
+
You can review the end-of-life dates in the update life cycle documentation for {product-title}. For more information, see _{product-title} update life cycle_.
77
+
====
78
+
+
79
+
.. Provide administrator approval based on your cluster update method:
80
+
** Individual updates: If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
81
+
** 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.
82
+
+
83
+
For information about administrator acknowledgment, see xref:./../upgrading/osd-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_osd-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
84
+
.. If you opted for recurring updates, select a preferred day of the week and upgrade start time in UTC from the drop-down menus.
85
+
.. Optional: You can set a grace period for *Node draining* during cluster upgrades. A *1 hour* grace period is set by default.
86
+
.. Click *Next*.
87
+
+
88
+
[NOTE]
89
+
====
90
+
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].
91
+
====
92
+
93
+
. Review the summary of your selections and click *Create cluster* to start the cluster installation. The installation takes approximately 30-40 minutes to complete.
94
+
95
+
.Verification
96
+
97
+
* 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*.
0 commit comments