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.

Resource Requirements

Machines

Node poolNodesCPUMemoryPurpose
bootstrap14 cores8 GBRuns the installer, and can also serve as the platform image registry.
control-plane38 cores16 GiBControl plane and platform components.
infra316 cores48 GiBLogging, monitoring, the application gateway, and the registry.
  • 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.

Diskcontrol-planeinfra
IaaS
System disk100100
/var/lib/etcd20—
/var/lib/containerd150150
/var/lib/kubelet200200
/var/cpaas (persistent)100200
Raw disk for TopoLVM—750
Bare Metal
System disk, minimum / recommended512 / 1 TB512 / 1 TB
Raw disk for TopoLVM—1 TB
  • 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

Node poolIn install-config.yamlNotes
control-planecontrolPlaneKeep deployMode at the default value normal, not base.
infraA node group in computes[]Declare the infra label and taint on the node pool after the cluster is created.

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

FeatureSelectionStorage
MonitoringVictoriaMetricsTopoLVM
LoggingClickHouseTopoLVM
Application gatewayEnvoy Gateway (Gateway API)—
Application gateway VIPAn enterprise load balancer if available; otherwise MetalLB—
Registry for application images Registry, 1 replicaTopoLVM

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

PluginPurpose
Alauda Container Platform Advanced MonitoringMonitoring
Alauda Container Platform Log Storage ManagementLog storage management
Alauda Data Services Analytical Database E1Log storage (ClickHouse)
Alauda Data Services Streaming E1Log message queue (Kafka)
Alauda Container Platform Gateway API ControllerApplication gateway (Envoy Gateway)
Alauda Container Platform RegistryRegistry for application images

The Installation Steps state how to place monitoring, logging, the application gateway, and the registry on the infra nodes.

Installation Steps

StepTaskDocumentation
1Plan, and confirm which network flows apply.Plan, Communication Matrix
2Download the installation packages.Download
3Prepare the platform image registry and upload the images.Prepare an External Platform Image Registry, mirror-registry
4Meet the common prerequisites, and prepare the bootstrap node and the control plane endpoint.Prerequisites
5Meet the prerequisites of the provider.Provider Pages
6Plan the disks of each node pool, including the raw disks for TopoLVM, before you create the cluster.Fixed at Creation, Provider Pages
7Install the global cluster.Provider Pages
8Validate the installation.Validation
9Publish the Common Extensions, which the plugins in the following steps require.Publish the Common Extensions
10Declare the label and taint on the infra node pool.Create Infra Nodes on Alauda OS Nodes
11Install TopoLVM on the data disks of the infra nodes, before the plugins that use it.Install
12Install monitoring with TopoLVM storage, and set its node selector and tolerations in the plugin configuration to place it on the infra nodes.ACP Advanced Monitoring, Place VictoriaMetrics Workloads on Infra Nodes
13Install logging, ClickHouse and Kafka, with TopoLVM storage, and pin its Pods to the infra nodes in install.env as described below the table.Fast Install, Pin Pods to a Dedicated Node Pool
14Install Envoy Gateway, and set the node selector and tolerations of envoy-proxy in the EnvoyProxy resource to place it on the infra nodes.Install Envoy Gateway via Envoy Gateway Operator, envoy-proxy placement
15Provide the gateway VIP: from the enterprise load balancer, or with MetalLB and an address pool.MetalLB component placement, IP pool
16On Huawei Cloud Stack, run envoy-proxy with the host network behind the HCS ELB instead.hostNetwork in envoy-proxy
17Install the registry with TopoLVM storage, and set its node selector and tolerations in Config/cluster to place it on the infra nodes.Install the Registry, PVC storage
18Install the etcd backup plugin.etcd Backup and Restore
19Complete the other post-installation tasks.Next Steps
—Upgrade later.Upgrade Overview

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. Leave NODE_AFFINITY_VALUE empty, because the infra label has an empty value.
  • TOLERATION_KEY, TOLERATION_VALUE, and TOLERATION_EFFECT: node-role.kubernetes.io/infra, reserved, and NoSchedule, the infra taint.