Skip to content

Commit c0b831d

Browse files
authored
Merge pull request #73011 from mletalie/OSDOCS-9947
[OSDOCS-9947]:Update GCP Custom Instances in OSD Docs
2 parents a495a22 + 9f74c2d commit c0b831d

File tree

1 file changed

+48
-15
lines changed

1 file changed

+48
-15
lines changed

modules/sd-planning-considerations.adoc

Lines changed: 48 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@
66
[id="control-plane-and-infra-node-sizing-and-scaling-sd_{context}"]
77
= Control plane and infrastructure node sizing and scaling
88

9-
When you install a {product-title}
9+
When you install a {product-title}
1010
ifdef::openshift-rosa[]
11-
(ROSA)
11+
(ROSA)
1212
endif::[]
1313
cluster, the sizing of the control plane and infrastructure nodes are automatically determined by the compute node count.
1414

@@ -19,11 +19,21 @@ If you change the number of compute nodes in your cluster after installation, th
1919

2020
During the installation process, the sizing of the control plane and infrastructure nodes are dynamically calculated. The sizing calculation is based on the number of compute nodes in a cluster.
2121

22-
The following table lists the control plane and infrastructure node sizing that is applied during installation.
22+
The following
23+
ifdef::openshift-rosa[]
24+
table lists
25+
endif::[]
26+
ifdef::openshift-dedicated[]
27+
tables list
28+
endif::[]
29+
the control plane and infrastructure node sizing that is applied during installation.
2330

31+
ifdef::openshift-dedicated[]
32+
AWS control plane and infrastructure node size
33+
endif::[]
2434
[options="header",cols="3*"]
2535
|===
26-
| Number of compute nodes |Control plane size |Infrastructure node size
36+
|Number of compute nodes |Control plane size |Infrastructure node size
2737

2838
|1 to 25
2939
|m5.2xlarge
@@ -33,21 +43,44 @@ The following table lists the control plane and infrastructure node sizing that
3343
|m5.4xlarge
3444
|r5.2xlarge
3545

36-
|101 to 180 ^[1]^
46+
|101 to 180
3747
|m5.8xlarge
3848
|r5.4xlarge
3949
|===
40-
[.small]
41-
--
42-
1. The maximum number of compute nodes on
50+
51+
ifdef::openshift-dedicated[]
52+
53+
GCP control plane and infrastructure node size
54+
[options="header",cols="3*"]
55+
|===
56+
|Number of compute nodes |Control plane size |Infrastructure node size
57+
58+
|1 to 25
59+
|custom-8-32768
60+
|custom-4-32768-ext
61+
62+
|26 to 100
63+
|custom-16-65536
64+
|custom-8-65536-ext
65+
66+
|101 to 180
67+
|custom-32-131072
68+
|custom-16-131072-ext
69+
|===
70+
71+
endif::[]
72+
73+
[NOTE]
74+
====
75+
The maximum number of compute nodes on
4376
ifdef::openshift-rosa[]
44-
ROSA
77+
ROSA
4578
endif::[]
4679
ifdef::openshift-dedicated[]
47-
{product-title}
80+
{product-title}
4881
endif::[]
4982
is 180.
50-
--
83+
====
5184

5285
[id="node-scaling-after-installation_{context}"]
5386
== Node scaling after installation
@@ -69,19 +102,19 @@ The maximum number of compute nodes on ROSA is 180.
69102

70103
.Rules for infrastructure node resizing alerts
71104

72-
Resizing alerts are triggered for the infrastructure nodes in a cluster when it has high-sustained CPU or memory utilization. This high-sustained utilization status is:
105+
Resizing alerts are triggered for the infrastructure nodes in a cluster when it has high-sustained CPU or memory utilization. This high-sustained utilization status is:
73106

74107
* Infrastructure nodes sustain over 50% utilization on average in a classic ROSA cluster with a single availability zone using 2 infrastructure nodes.
75108
* Infrastructure nodes sustain over 66% utilization on average in a classic ROSA cluster with multiple availability zones using 3 infrastructure nodes.
76109
+
77110
[NOTE]
78111
====
79-
The maximum number of compute nodes on
112+
The maximum number of compute nodes on
80113
ifdef::openshift-rosa[]
81-
ROSA
114+
ROSA
82115
endif::[]
83116
ifdef::openshift-dedicated[]
84-
{product-title}
117+
{product-title}
85118
endif::[]
86119
is 180.
87120

0 commit comments

Comments
 (0)