Single Cluster
The global cluster also runs the business workloads. Disaster recovery is not used. For the assumptions that apply to every scenario, see Common Assumptions.
These sizes match the tier of 24 worker nodes and 500 namespaces in Global Cluster as a Workload Cluster. For a different number of worker nodes or namespaces, select the matching tier on that page.
TOC
Resource RequirementsMachinesDisksNode PoolsControl Plane EndpointSolution SelectionFeatures and StoragePlugins on Infra NodesInstallation StepsResource Requirements
Machines
- The tables give the minimum recommended size of each node. Physical servers are usually much larger, so select servers that are at least this size.
- The sizes follow the capacity tiers of each product component. After the installation, scale up according to the actual utilization.
- For ARM nodes, scale the sizes as described in Machines.
- Logging is planned for 5,000 log entries per second with 7 days of retention. For more logs, expand the disks.
- The number and size of worker nodes depend on the business workloads and are not covered here.
- 4 cores and 8 GB is the x86 minimum for the bootstrap node. For its disk and the arm64 minimum, see Bootstrap Node.
- If no image registry is available and machines are limited, use the bootstrap node as the platform image registry. See Using the Bootstrap Node as mirror-registry.
Disks
Sizes are per node, in GB. For what each disk holds and why it has this size, see Disk Configuration.
- On IaaS, the raw disk for TopoLVM is sized for the current need, because it can be expanded later. See Raw Disk for TopoLVM.
- The bootstrap node needs 300 GB or more for the extracted packages and
/var/cpaas.
Node Pools
- For the fields, see Installation Reference.
- For the infra label and taint, see Create Infra Nodes on Alauda OS Nodes.
Control Plane Endpoint
The control plane endpoint serves the Kubernetes API and the platform access address. Choose one of the following:
- Self-built VIP: needs no external device.
- Enterprise load balancer: allocate one VIP on it for the control plane endpoint. The VIP of the application gateway can also come from the same load balancer.
- Huawei Cloud Stack: use the ELB that the provider creates.
For what to prepare, see Confirm Install-Time Decisions and Plan the Control Plane Endpoint.
Solution Selection
Features and Storage
On Huawei Cloud Stack, do not use MetalLB for the gateway VIP. Run envoy-proxy with the host network, and put the HCS ELB in front of the gateway nodes. See How To Use hostNetwork In envoy-proxy.
Plugins on Infra Nodes
The Installation Steps state how to place monitoring, logging, the application gateway, and the registry on the infra nodes.
Installation Steps
For step 13, set the following values in install.env in place of the example values of the dedicated node pool:
NODE_AFFINITY_KEY:node-role.kubernetes.io/infra, the infra label. LeaveNODE_AFFINITY_VALUEempty, because the infra label has an empty value.TOLERATION_KEY,TOLERATION_VALUE, andTOLERATION_EFFECT:node-role.kubernetes.io/infra,reserved, andNoSchedule, the infra taint.