#Prerequisites

Before installing the global cluster, you need to prepare hardware, network, and OS that meet the requirements.

#Resource Planning

This section provides guidelines for resource planning before installing . Choose the appropriate deployment scenario based on your environment and usage needs, and prepare resources accordingly.

#Deployment Architectures

Before installation, you must determine which deployment architecture best fits your use case. supports the following three common deployment architectures:

• Multi-Cluster

  Select this architecture if you need to centrally manage multiple Kubernetes clusters. In this mode, consists of one Global cluster and multiple workload clusters. Running non-platform workloads on the Global cluster may degrade platform stability and performance, and should be avoided.

• Single Cluster

  Select this architecture if you plan to install only one cluster and run workloads directly on it. In this mode, the Global cluster also acts as a workload cluster, and therefore requires more resources compared with a pure Global-only setup in Multi-Cluster mode.

• Single Node

  WARNING

  This architecture is intended solely for testing or proof-of-concept purposes and should not be used in production.

#Single Node

The following table lists the minimum hardware requirements for installing in Single Node mode.

Resource	Minimum Requirement
CPU	12 cores
Memory	24GB
Storage	Storage Capacity

#Single Cluster

In this mode, the Global cluster serves both as the control plane and as the workload cluster.
The number of control plane nodes of global cluster MUST be 3.

The total resource requirement consists of two parts:

• Base resources for the Global cluster itself
• Additional resources for running workloads on the same cluster

The resources required for a highly available Global cluster are as follows:

Resource	Minimum Requirement
CPU	8 cores
Memory	16GB
Storage	Storage Capacity

To estimate the additional resources required for your workloads, refer to Evaluating Resources for Workload Cluster

#Multi-Cluster

When managing multiple workload clusters, the resource usage of the Global cluster increases proportionally with the number of managed clusters. The additional overhead mainly comes from cluster registration, monitoring, and control-plane synchronization.

To estimate the resources required for your Global cluster based on the number of managed clusters, refer to Evaluating Resources for Global Cluster

#Network

Before installation, the following network resources must be pre-configured. If a hardware LoadBalancer cannot be provided, the installer supports configuring haproxy + keepalived as a software load balancer, but you need to understand:

• Poorer Performance: Software load balancing performance is lower than hardware LoadBalancer.
• Higher Complexity: If you are not familiar with keepalived, it may cause the global cluster to be unavailable, problem troubleshooting will take a long time, and seriously affect platform reliability.

#Network Resources

Resource	Mandatory	Quantity	Description
global VIP	Mandatory	1	Used for nodes in the cluster to access kube-apiserver, configured in the load balancing device to ensure high availability. This IP can also be used as the access address for the platform Web UI. Workload clusters in the same network as the global cluster can also access the global cluster through this IP.
External IP	Optional	On Demand	When there are workload clusters that are not in the same network as the global cluster, such as a hybrid cloud scenario, it must be provided. Workload clusters in other networks access the global cluster through this IP. This IP needs to be configured in the load balancing device to ensure high availability. This IP can also be used as the access address for the platform Web UI.
Domain Name	Optional	On Demand	If you need to access the global cluster or platform Web UI through a domain name, please provide it in advance and ensure that the domain name resolution is correct.
Certificate	Optional	On Demand	It is recommended to use a trusted certificate to avoid browser security warnings; if not provided, the installer will generate a self-signed certificate, but there may be security risks when using HTTPS.

#Network Configuration

Type	Requirement Description
Network Speed	Speed of global cluster and workload cluster in the same network ≥1Gbps (recommended 10Gbps); cross-network speed ≥100Mbps (recommended 1Gbps). Insufficient speed will significantly reduce data query performance.
Network Latency	Latency ≤10 ms within the same cluster; latency ≤100 ms (recommended ≤30 ms) across clusters.
Network Policy	Please refer to LoadBalancer Forwarding Rules to ensure that the necessary ports are open; when using Calico CNI, ensure that the IP-in-IP protocol is enabled.
IP Address Range	The global cluster nodes should avoid using the 172.16-32 network segment. If it has been used, please adjust the Docker configuration (add the bip parameter) to avoid conflicts.

#LoadBalancer Forwarding Rules

This rule is designed to ensure that the global cluster can receive traffic from the LoadBalancer normally. Please check the network policy according to the following table to ensure that the relevant ports are open.

Source IP	Protocol	Destination IP	Destination Port	Description
global VIP, External IP	TCP	All control plane node IPs	443	Provides access services for the platform Web UI, image repository, and Kubernetes API Server through the HTTPS protocol. The default port is 443. If you need to use a custom HTTPS port, please do the following: Replace the destination port in the port forwarding rule with your custom port number. Later, in the Web UI installation parameters, fill in your custom port number.
global VIP, External IP	TCP	All control plane node IPs	6443	This port provides access to the Kubernetes API Server for nodes within the cluster.
global VIP, External IP	TCP	All control plane node IPs	11443	This port provides access to the image repository for nodes within the cluster. Note: If you plan to use an external image repository instead of the default image repository provided by the global cluster, you do not need to configure this port.