Create a Cluster on Alauda OS
On this path, creates clusters whose nodes run Alauda OS, an image-based, read-only operating system. The nodes are virtual machines on Huawei DCS, Huawei Cloud Stack, or VMware vSphere, or physical servers on Bare Metal.
TOC
ArchitectureWhatac Does and What the Platform DoesNodes Are Replaced, Not Changed in PlaceFixed at CreationSupported ProvidersControl Plane EndpointInstall the Providers on the global ClusterCluster Creation WorkflowRelated TasksArchitecture
A cluster on Alauda OS is described by Cluster API objects on the global cluster. Two providers run on global and act on those objects:
- The Alauda Container Platform Cluster Bootstrap Provider turns machines into Kubernetes nodes with kubeadm and runs the control plane.
- An infrastructure provider, one for each IaaS platform, creates the machines from Alauda OS images. On Bare Metal, it reinstalls physical servers that you have registered instead of creating virtual machines.

What ac Does and What the Platform Does
You create a cluster with ac adm alpha cluster create. ac renders the Cluster API and provider objects from one install-config.yaml, checks them, and applies them to the global cluster. From then on, the providers on global create the machines and keep the cluster running. Node changes are covered in Manage Nodes on Alauda OS Clusters, and version changes in the upgrade documentation.
Nodes Are Replaced, Not Changed in Place
A Kubernetes or Alauda OS version change replaces the nodes one at a time. On Huawei DCS, Huawei Cloud Stack, and VMware vSphere, each node is replaced with a new virtual machine. On Bare Metal, the existing hosts are reinstalled; a host removed from the cluster returns to its pool, and its declared data volumes stay with that host. The replacement node gets the same host, and its data volumes, only when the pool has no other available host. Supported OS settings are changed through Machine Configuration.
A cluster with a single control plane node is for testing and cannot be upgraded.
Fixed at Creation
Decide the following before you create the cluster. They cannot be changed on an existing cluster:
- The control plane endpoint mode and address. See Plan the Control Plane Endpoint.
- The image registry of the cluster: the registry of the
globalcluster or a dedicated one. See Choose the Image Registry for a Workload Cluster. - On Huawei DCS, Huawei Cloud Stack, and VMware vSphere, the layout of an existing persistent disk, such as its size and, on Huawei DCS, its datastore. On VMware vSphere, the addresses and disks of a pool slot are also fixed once a machine takes the slot. Plan the disks of each node pool before you create the cluster.
Supported Providers
Control Plane Endpoint
What to prepare for each endpoint mode is in Plan the Control Plane Endpoint.
Install the Providers on the global Cluster
Install the provider for the IaaS platform, and the Cluster Bootstrap Provider, on the global cluster as described in Install the Infrastructure Provider. A global cluster installed with ac already runs the Cluster Bootstrap Provider and the provider of its own platform.
Upgrading Kubernetes on an Alauda OS global cluster also requires the provider for that IaaS platform to be uploaded and installed on the global cluster first.
Cluster Creation Workflow
Create a workload cluster on Alauda OS in the following order. Prepare describes the first three steps in the same order.
- Install the Provider: Install the provider for your IaaS platform, and the Cluster Bootstrap Provider, on the
globalcluster. - Infrastructure Resources: Prepare what the provider requires, as listed in its Prerequisites page. With
ac, this is mainly the credential Secret and the IaaS objects thatinstall-config.yamlnames. - Plan the Cluster: Read Prepare for the decisions that apply to every provider, such as the control plane endpoint mode and the image registry of the cluster. Also check the following before you create the cluster:
- Node Labels and Taints: If dedicated node pools (monitoring, logging, ingress) are planned, read how to declare role labels and taints on the pool in Infra Nodes before creating the pools.
- CPU Baseline: For x86_64 cluster nodes that use ACP-provided Alauda OS images, the underlying CPUs must support the
x86-64-v2ISA baseline. For details, see OS Support Matrix.
- Create a Cluster: Create the cluster, including its first worker nodes, with
ac adm alpha cluster createfrom oneinstall-config.yaml.
Each provider has its own pages for these steps:
If a failure is not provider-specific, see Troubleshooting.