Home > Communication Service Provider Solutions > Telecom Multicloud Foundation > Red Hat > Guides > Red Hat Open Shift Container Platform Guides > Reference Architecture Guide: Dell Technologies - Red Hat OpenShift Reference Architecture for Telecom > Cluster scaling
The design and architecture of OpenShift Container Platform place resource hosting limits on an OpenShift cluster. The following table shows the limits:
Resources |
Limit |
Nodes per cluster |
500 |
Pods per cluster |
62,500 |
Pods per node |
500 |
Pods per core |
Not specified—limited by maximum pods per node |
Namespaces per cluster |
10,000 |
Number of builds |
10,000 (based on 512 MB RAM per image) |
Pods per namespace |
25,000 |
Services per cluster |
10,000 |
Services per namespace |
5,000 |
Back-ends per service |
5,000 |
Deployments per namespace |
2,000 |
Red Hat offers support for OpenShift Container Platform 4.6 up to these limits, as described in Planning your environment according to object maximums.
Our minimum recommended control-plane node configuration is a PowerEdge R650 server with dual Intel® Gold 6330 CPUs and 192 GB RAM. As the Red Hat resource requirements show, this node is large enough for a 250-node cluster and higher. Dell Technologies recommends that you do not scale beyond 200 nodes, which means that the proposed reference design is sufficient for nearly all deployments. The following table shows node sizing recommendations:
Number of compute nodes |
CPU cores* |
Memory (GB) |
25 |
4 |
16 |
100 |
8 |
32 |
200 |
16 |
64 |
*Does not include provisioning of at least four cores per node for infrastructure I/O handling.