1.3. Control plane and infrastructure node sizing and scaling
When you install an OpenShift Dedicated cluster, the sizing of the control plane and infrastructure nodes are automatically determined by the compute node count.
If you change the number of compute nodes in your cluster after installation, the Red Hat Site Reliability Engineering (SRE) team scales the control plane and infrastructure nodes as required to maintain cluster stability.
1.3.1. Node sizing during installation 링크 복사링크가 클립보드에 복사되었습니다!
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.
The following tables list the control plane and infrastructure node sizing that is applied during installation.
AWS control plane and infrastructure node size:
| Number of compute nodes | Control plane size | Infrastructure node size |
|---|---|---|
| 1 to 25 | m5.2xlarge | r5.xlarge |
| 26 to 100 | m5.4xlarge | r5.2xlarge |
| 101 to 249 | m5.8xlarge | r5.4xlarge |
Google Cloud control plane and infrastructure node size:
| Number of compute nodes | Control plane size | Infrastructure node size |
|---|---|---|
| 1 to 25 | custom-8-32768 | custom-4-32768-ext |
| 26 to 100 | custom-16-65536 | custom-8-65536-ext |
| 101 to 249 | custom-32-131072 | custom-16-131072-ext |
Google Cloud control plane and infrastructure node size for clusters created on or after 21 June 2024:
| Number of compute nodes | Control plane size | Infrastructure node size |
|---|---|---|
| 1 to 25 | n2-standard-8 | n2-highmem-4 |
| 26 to 100 | n2-standard-16 | n2-highmem-8 |
| 101 to 249 | n2-standard-32 | n2-highmem-16 |
The maximum number of compute nodes on OpenShift Dedicated clusters version 4.14.14 and later is 249. For earlier versions, the limit is 180.