Skip to content

Commit ff139d4

Browse files
authored
Merge pull request #63960 from EricPonvelle/OSDOCS-6922_InfraNode_Scaling
OSDOCS-6922: Infrastructure Node Utilization Update
2 parents 6ca0778 + 4bf08ee commit ff139d4

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

modules/sd-planning-considerations.adoc

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,10 +70,10 @@ The maximum number of compute nodes on ROSA is 180.
7070

7171
.Rules for infrastructure node resizing alerts
7272

73-
Resizing alerts are triggered for the infrastructure nodes in a cluster when either of the following scenarios are true:
73+
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:
7474

75-
* Each infrastructure node has less than 16GiB RAM or less than 5 CPUs, and there are more than 25 and less than 101 compute nodes.
76-
* Each infrastructure node has less than 32GiB RAM or less than 9 CPUs, and there are more than 100 compute nodes.
75+
* Infrastructure nodes sustain over 50% utilization on average in a classic ROSA cluster with a single availability zone using 2 infrastructure nodes.
76+
* Infrastructure nodes sustain over 66% utilization on average in a classic ROSA cluster with multiple availability zones using 3 infrastructure nodes.
7777
+
7878
[NOTE]
7979
====
@@ -85,6 +85,8 @@ ifdef::openshift-dedicated[]
8585
{product-title}
8686
endif::[]
8787
is 180.
88+
89+
The resizing alerts only appear after sustained periods of high utilization. Short usage spikes, such as a node temporarily going down causing the other node to scale up, do not trigger these alerts.
8890
====
8991

9092
The SRE team might scale the control plane and infrastructure nodes for additional reasons, for example to manage an increase in resource consumption on the nodes.

0 commit comments

Comments
 (0)