| title | Cluster Sizing |
|---|---|
| weight | 20 |
| aliases | /medical-diagnosis/cluster-sizing/ |
To understand cluster sizing requirements for the {med-pattern}, consider the following components that the {med-pattern} deploys on the datacenter or the hub OpenShift cluster:
| Name | Kind | Namespace | Description |
|---|---|---|---|
Medical Diagnosis Hub |
Application |
medical-diagnosis-hub |
Hub GitOps management |
{rh-gitops} |
Operator |
openshift-operators |
{rh-gitops-short} |
{rh-ocp-data-first} |
Operator |
openshift-storage |
Cloud Native storage solution |
{rh-amq-streams} |
Operator |
openshift-operators |
AMQ Streams provides Apache Kafka access |
{rh-serverless-first} |
Operator |
- knative-serving (knative-eventing) |
Provides access to Knative Serving and Eventing functions |
: Removed the following in favor of the link to OCP docs The minimum requirements for an {ocp} cluster depend on your installation platform. For instance, for AWS, see Installing {ocp} on AWS, and for bare-metal, see Installing {ocp} on bare metal.
For information about requirements for additional platforms, see {ocp} documentation.
The {med-pattern} has been tested with a defined set of configurations that represent the most common combinations that {ocp} customers are using for the x86_64 architecture.
For {med-pattern}, the OpenShift cluster size must be a bit larger to support the compute and storage demands of OpenShift Data Foundations and other Operators.
|
Note
|
You might want to add resources when more developers are working on building their applications. |
The OpenShift cluster is a standard deployment of 3 control plane nodes and 3 or more worker nodes.
| Node type | Number of nodes | Cloud provider | Instance type |
|---|---|---|---|
Control plane and worker |
3 and 3 |
Google Cloud |
n1-standard-8 |
Control plane and worker |
3 and 3 |
Amazon Cloud Services |
m5.2xlarge |
Control plane and worker |
3 and 3 |
Microsoft Azure |
Standard_D8s_v3 |