About OpenShift cluster sizing for the Intel AMX accelerated Multicloud GitOps pattern
The minimum requirements for an OpenShift Container Platform cluster depend on your installation platform, for example:
For AWS, see Installing OpenShift Container Platform on AWS.
For bare-metal, see Installing OpenShift Container Platform on bare metal.
To understand cluster sizing requirements for the Intel AMX accelerated Multicloud GitOps pattern, consider the following components that the Intel AMX accelerated Multicloud GitOps pattern deploys on the datacenter or the hub OpenShift cluster:
| Name | Kind | Namespace | Description |
|---|---|---|---|
multicloud-gitops-amx-hub | Application | multicloud-gitops-amx-hub | Hub GitOps management |
Red Hat Advanced Cluster Management | Operator | open-cluster-management | Advance Cluster Management |
Red Hat OpenShift GitOps | Operator | openshift-operators | OpenShift GitOps |
Node Feature Discovery | Operator | openshift-nfd | Manages the detection and labeling of hardware features and configuration (for example Intel AMX) |
Red Hat OpenShift Data Foundation | Operator | openshift-storage | Cloud Native storage solution |
The Intel AMX accelerated Multicloud GitOps pattern also includes the Red Hat Advanced Cluster Management (RHACM) supporting operator that is installed by OpenShift GitOps using Argo CD.
Intel AMX accelerated Multicloud GitOps pattern with OpenShift clusters sizes
The datacenter hub OpenShift cluster needs to be a bit bigger than the Factory/Edge clusters because this is where the developers will be running pipelines to build and deploy the Intel AMX accelerated Multicloud GitOps pattern on the cluster. The above cluster sizing is close to a minimum size for a Datacenter HUB cluster. In the next few sections we take some snapshots of the cluster utilization while the Intel AMX accelerated Multicloud GitOps pattern is running. Keep in mind that resources will have to be added as more developers are working building their applications.
The recommended clusters sizes for datacenter hub and for managed datacenter are the same in this case:
| Node type | Number of nodes | CPU | Memory | Storage |
|---|---|---|---|---|
Control Planes | 3 | 4th Generation Intel Xeon Gold 6426Y (16 cores at 2.5 GHz base/3.3 GHz all core turbo/3.0 GHz AMX all core turbo) or better | 128 GB (8 x 16 GB DDR5 4800) or more | NVME SSD 3TB or more |
Workers | 3 | 4th Generation Intel Xeon Gold 6438Y+ (32 cores at 2.0 GHz base/2.8 GHz all core turbo/2.4 GHz AMX all core turbo) or better | 256 GB (16 x 16 GB) or 512 GB (16 x 32GB) DDR5-4800 | NVME SSD 3TB or more |
You might want to add resources when more developers are working on building their applications. |
The pattern was tested in the on-premises environment with following hardware configuration (per cluster):
| Node type | Number of nodes | CPU | Memory | Storage |
|---|---|---|---|---|
Control Planes + Workers | 3 + 3 | 4th Generation Intel Xeon Platinum 8460Y+ Processor (40 cores at 2.0 GHz base/2.8 GHz all core turbo/2.6 AMX all core turbo) | 512 GB (16x32GB DDR5 4800) | 4x 3.84TB U.2 NVMe PCIe Gen4 |
