Evaluating Resources for Global Cluster
TOC
OverviewNode SizingBaseline Production SizingVertical Scaling GuidelinesHorizontal Scaling GuidelinesResource Validation and MonitoringGlobal Cluster as a Workload ClusterSummaryOverview
Use these resource evaluation practices when planning the global cluster. The sizing depends on how the global cluster is used:
- In a Multi-Cluster deployment, the
globalcluster runs only the platform. Select the tier by the number of managed clusters; see Node Sizing. - In a Single Cluster deployment, the
globalcluster also serves as the workload cluster. Select the tier by the number of worker nodes; see Global Cluster as a Workload Cluster.
Proper node sizing helps the global cluster manage registered clusters, handle synchronization traffic, and process user API and Web Console requests within the performance expectations of your environment.
Node Sizing
This section applies to the global cluster of a Multi-Cluster deployment.
The global cluster is responsible for:
- Maintaining cluster registration and metadata.
- Handling inbound API requests from the Web Console and CLI.
- Coordinating synchronization and heartbeat messages with connected clusters.
- Managing internal controllers and resource reconciliation loops.
Because the global cluster handles both management operations and data aggregation from all connected clusters, plan resource allocation according to the expected scale and workload intensity.
Baseline Production Sizing
The production-scale sizing depends primarily on:
- Number of managed clusters
- Frequency of synchronization cycles
- Concurrent API request rate (from users or automation)
- Volume of streaming requests
- Number of plugins installed
The following table provides reference configurations validated through internal performance testing.
These recommendations are general guidelines. Actual requirements depend on your cluster topology, user concurrency, and plugins installed.
Vertical Scaling Guidelines
When increasing load per node (for example, 2× more clusters or higher user concurrency), follow these adjustments:
Horizontal Scaling Guidelines
When exceeding 100 managed clusters or encountering persistent API latency above 500 ms:
Add nodes to distribute request handling and controller workloads.
Resource Validation and Monitoring
After deployment, continuously monitor the following metrics to validate node sizing:
If sustained resource usage consistently exceeds recommended thresholds, scale vertically (add CPU/memory) or horizontally (add nodes) before user-facing performance degradation occurs.
Global Cluster as a Workload Cluster
In a Single Cluster deployment, the global cluster also serves as the workload cluster. Size its control plane nodes by the number of worker nodes with the following table. The workload cluster table in Evaluating Resources for Workload Cluster does not apply directly, for these reasons:
- The
globalcluster runs the platform management components in addition to the control plane of the workload cluster. - As the number of nodes grows, the load on the
globalcluster grows faster than the node count. Larger clusters usually run more features, hold more custom resources, and send more requests to the API server.
The headroom guidance for workload clusters also applies: target an overall CPU and memory utilization of about 60% or less; see Control Plane Node Sizing.
Summary
When sizing the global cluster of a Multi-Cluster deployment:
- Begin with 3 nodes × 16 cores × 32 GB for moderate-scale deployments (≤50 clusters).
- Scale vertically for higher request concurrency or heavy Web Console usage.
- Scale horizontally beyond 100 clusters to maintain API responsiveness.
- Re-evaluate sizing after every significant increase in managed cluster count or sync frequency.
Use these practices to keep resource planning aligned with the growth of your Multi-Cluster environment.