About OpenShift cluster sizing for the Multicloud GitOps Pattern
Support matrix for Multicloud GitOps pattern
The Multicloud GitOps pattern has been tested in the following Certified Cloud Providers.
| Certified Cloud Providers | 4.8 | 4.9 | 4.10 |
|---|---|---|---|
| Amazon Web Services | :heavy_check_mark: | ||
| Microsoft Azure | :heavy_check_mark: | ||
| Google Cloud Platform | :heavy_check_mark: |
Minimum requirements for OpenShift Container Platform
OpenShift 4 has the following minimum requirements for sizing of nodes:
- Minimum 4 vCPU** (additional are strongly recommended)
- Minimum 16 GB RAM** (additional memory is strongly recommended, especially if
etcdis colocated on Control Planes) - Minimum 40 GB hard disk space for the file system containing
/var/ - Minimum 1 GB hard disk space for the file system containing
/usr/local/bin/
There is one application that comprises the Medical Diagnosis pattern. In addition, the Multicloud GitOps pattern also includes the Red Hat Advanced Cluster Management (RHACM) supporting operator that is installed by OpenShift GitOps using ArgoCD.
Understanding Multicloud GitOps pattern components
Here’s an inventory of what gets deployed by the Multicloud GitOps pattern on the Datacenter/Hub OpenShift cluster:
| Name | Kind | Namespace | Description |
|---|---|---|---|
| multicloud-gitops-hub | Application | multicloud-gitops-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 |
Multicloud GitOps pattern with OpenShift datacenter hub cluster size
The Multicloud GitOps pattern has been tested with a defined set of specifically tested configurations that represent the most common combinations that Red Hat OpenShift Container Platform (OCP) customers are using or deploying for the x86_64 architecture.
The datacenter hub OpenShift cluster is made up of the the following on the AWS deployment tested:
| Node Type | Number of nodes | Cloud Provider | Instance Type |
|---|---|---|---|
| Control Plane | 4 | Amazon Web Services | m5.xlarge |
| Worker | 3 | Amazon Web Services | m5.xlarge |
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 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 Multicloud GitOps pattern is running. Keep in mind that resources will have to be added as more developers are working building their applications.
Datacenter cluster utilization
Below is a snapshot of the OpenShift cluster utilization while running the Multicloud GitOps pattern:
| CPU | Memory | File System | Network | Pod Count |
|---|
Multicloud GitOps pattern with OpenShift managed datacenter cluster size
The OpenShift cluster is a standard datacenter deployment of 3 control plane nodes and 3 or more worker nodes.
| Node Type | Number of nodes | Cloud Provider | Instance Type |
|---|---|---|---|
| Control Plane/Worker | 3 | Google Cloud | n1-standard-8 |
| Control Plane/Worker | 3 | Amazon Cloud Services | m5.2xlarge |
| Control Plane/Worker | 3 | Microsoft Azure | Standard_D8s_v3 |
Managed Datacenter Cluster Utilization
GCP
This is a snapshot of a Google Cloud managed data center cluster running the production Multicloud GitOps pattern.
| CPU | Memory | File System | Network | Pod Count |
|---|
AWS
This is a snapshot of a Amazon Web Services managed data center cluster running the production Multicloud GitOps pattern.
| CPU | Memory | File System | Network | Pod Count |
|---|
Azure
This is a snapshot of an Azure managed data center cluster running the production Multicloud GitOps pattern.
| CPU | Memory | File System | Network | Pod Count |
|---|
AWS Instance Types
The Multicloud GitOps pattern was tested with the highlighted AWS instances in bold. The OpenShift installer will let you know if the instance type meets the minimum requirements for a cluster.
The message that the openshift installer will give you will be similar to this message
INFO Credentials loaded from default AWS environment variables
FATAL failed to fetch Metadata: failed to load asset "Install Config": [controlPlane.platform.aws.type: Invalid value: "m4.large": instance type does not meet minimum resource requirements of 4 vCPUs, controlPlane.platform.aws.type: Invalid value: "m4.large": instance type does not meet minimum resource requirements of 16384 MiB Memory]
Below you can find a list of the AWS instance types that can be used to deploy the Multicloud GitOps pattern.
| Instance type | Default vCPUs | Memory (GiB) | Datacenter | Factory/Edge |
|---|---|---|---|---|
| 3x3 OCP Cluster | 3 Node OCP Cluster | |||
| m4.xlarge | 4 | 16 | N | N |
| m4.2xlarge | 8 | 32 | Y | Y |
| m4.4xlarge | 16 | 64 | Y | Y |
| m4.10xlarge | 40 | 160 | Y | Y |
| m4.16xlarge | 64 | 256 | Y | Y |
| m5.xlarge | 4 | 16 | Y | N |
| m5.2xlarge | 8 | 32 | Y | Y |
| m5.4xlarge | 16 | 64 | Y | Y |
| m5.8xlarge | 32 | 128 | Y | Y |
| m5.12xlarge | 48 | 192 | Y | Y |
| m5.16xlarge | 64 | 256 | Y | Y |
| m5.24xlarge | 96 | 384 | Y | Y |
The OpenShift cluster is made of 4 Control Plane nodes and 3 Workers for the Datacenter and the Edge/managed data center cluster are made of 3 Control Plane and 3 Worker nodes. For the node sizes we used the m5.xlarge on AWS and this instance type met the minimum requirements to deploy the Multicloud GitOps pattern successfully on the Datacenter hub. On the managed data center cluster we used the m5.xlarge since the minimum cluster was comprised of 3 nodes. .
To understand better what types of nodes you can use on other Cloud Providers we provide some of the details below.
Azure Instance Types
The Multicloud GitOps pattern was also deployed on Azure using the Standard_D8s_v3 VM size. Below is a table of different VM sizes available for Azure. Keep in mind that due to limited access to Azure we only used the Standard_D8s_v3 VM size.
The OpenShift cluster is made of 3 Control Plane nodes and 3 Workers for the Datacenter cluster.
The OpenShift cluster is made of 3 Control Plane nodes and 3 or more workers for each of the managed data center clusters.
| Type | Sizes | Description |
|---|---|---|
| General purpose | B, Dsv3, Dv3, Dasv4, Dav4, DSv2, Dv2, Av2, DC, DCv2, Dv4, Dsv4, Ddv4, Ddsv4 | Balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers. |
| Compute optimized | F, Fs, Fsv2, FX | High CPU-to-memory ratio. Good for medium traffic web servers, network appliances, batch processes, and application servers. |
| Memory optimized | Esv3, Ev3, Easv4, Eav4, Ev4, Esv4, Edv4, Edsv4, Mv2, M, DSv2, Dv2 | High memory-to-CPU ratio. Great for relational database servers, medium to large caches, and in-memory analytics. |
| Storage optimized | Lsv2 | High disk throughput and IO ideal for Big Data, SQL, NoSQL databases, data warehousing and large transactional databases. |
| GPU | NC, NCv2, NCv3, NCasT4_v3, ND, NDv2, NV, NVv3, NVv4 | Specialized virtual machines targeted for heavy graphic rendering and video editing, as well as model training and inferencing (ND) with deep learning. Available with single or multiple GPUs. |
| High performance compute | HB, HBv2, HBv3, HC, H | Our fastest and most powerful CPU virtual machines with optional high-throughput network interfaces (RDMA). |
For more information please refer to the Azure VM Size Page.
Google Cloud (GCP) Instance Types
The Multicloud GitOps pattern was also deployed on GCP using the n1-standard-8 VM size. Below is a table of different VM sizes available for GCP. Keep in mind that due to limited access to GCP we only used the n1-standard-8 VM size.
The OpenShift cluster is made of 3 Control Plane and 3 Workers for the Datacenter cluster.
The OpenShift cluster is made of 3 Nodes combining Control Plane/Workers for the Edge/managed data center cluster.
The following table provides VM recommendations for different workloads.
| General purpose | Workload optimized
| Cost-optimized | Balanced | Scale-out optimized | Memory-optimized | Compute-optimized | Accelerator-optimized |
|---|---|---|---|---|---|
| E2 | N2, N2D, N1 | T2D | M2, M1 | C2 | A2 |
| Day-to-day computing at a lower cost | Balanced price/performance across a wide range of VM shapes | Best performance/cost for scale-out workloads | Ultra high-memory workloads | Ultra high performance for compute-intensive workloads | Optimized for high performance computing workloads |
For more information please refer to the GCP VM Size Page.
