Alauda OS Support Matrix
This document lists the versions of Kubernetes components included in different Alauda OS images.
TOC
CPU BaselineDownloading Alauda OSOS VariantsMixed Architecture within a ClusterVersion MappingImage Format by ProviderCPU Baseline
ACP-provided Alauda OS images on x86_64 require CPUs that meet the x86-64-v2 ISA baseline. x86_64 hardware that does not support x86-64-v2 is outside the supported baseline for these images.
This requirement applies when you create or upgrade cluster nodes with ACP-provided Alauda OS images.
Downloading Alauda OS
Download the Alauda OS image for your ACP release from the OS download page in Customer Portal. That page is the authoritative list of the images published for each ACP release; image file names are not reproduced here. The infrastructure provider version, the Alauda OS image version, and the ACP version must match, except during an upgrade, when nodes also use the images of intermediate Kubernetes versions, as described in ACP Version and Kubernetes Version.
An ACP release can publish more than one image — one per architecture, and from ACP v4.4.0 more than one OS variant; see OS Variants. Every image published for the same ACP release contains the component versions listed in that release's row below, so select the download by your node architecture and by the artifact format your provider requires. See Image Format by Provider.
OS Variants
The variant of an image is part of its name, for example m55 in alaudaos-45.m55.<timestamp>-0. Alauda OS KO and Alauda OS KU are the Alauda OS K variants.
- Huawei DCS: for a template of an Alauda OS K variant, set
provider.dcs.osType: alaudaos-k; see Writeinstall-config.yaml. - Huawei Cloud Stack and VMware vSphere: every variant works without a setting.
- Bare Metal: the OS of a host is the
os.baremetal.alauda.io/idlabel of its registration,alaudaos.m.55for Alauda OS M55 andalaudaos.k.25for Alauda OS KU.
Mixed Architecture within a Cluster
In a cluster that mixes architectures, every VM template or image ConfigMap must set architecture; see VM Template ConfigMap for Huawei DCS and Image ConfigMap for Huawei Cloud Stack.
Version Mapping
| ACP Version | Kubernetes Version | containerd | etcd |
|---|---|---|---|
| v4.0.0 | v1.31.6 | 1.7.23-4 | v3.5.18 |
| v4.0.1 | v1.31.6 | 1.7.23-4 | v3.5.18 |
| v4.0.2 | v1.31.6 | 1.7.23-4 | v3.5.21 |
| v4.0.3 | v1.31.6-1 | 1.7.23-4 | v3.5.21 |
| v4.0.4 | v1.31.12 | 1.7.23-4 | v3.5.21 |
| v4.0.5 | v1.31.12 | 1.7.23-4 | v3.5.21 |
| v4.0.6 | v1.31.12 | 1.7.23-4 | v3.5.21 |
| v4.0.7 | v1.31.12 | 1.7.23-4 | v3.5.21 |
| v4.0.8 | v1.31.14-1 | 1.7.23-4 | v3.5.25-251215 |
| v4.0.9 | v1.31.14-2 | 1.7.23-4 | v3.5.25-251215 |
| v4.0.10 | v1.31.14-2 | 1.7.23-4 | v3.5.25-251215 |
| v4.0.11 | v1.31.14-2 | 1.7.23-4 | v3.5.25-251215 |
| v4.0.12 | v1.31.14-2 | 1.7.23-4 | v3.5.25-251215 |
| v4.1.0 | v1.32.7 | 1.7.27-4 | v3.5.21 |
| v4.1.1 | v1.32.7 | 1.7.27-4 | v3.5.21 |
| v4.1.2 | v1.32.7 | 1.7.27-4 | v3.5.21 |
| v4.1.3 | v1.32.7 | 1.7.27-4 | v3.5.21 |
| v4.1.4 | v1.32.11-1 | 1.7.27-4 | v3.5.25-251215 |
| v4.1.5 | v1.32.11-2 | 1.7.27-4 | v3.5.25-251215 |
| v4.1.6 | v1.32.11-2 | 1.7.27-4 | v3.5.25-251215 |
| v4.1.7 | v1.32.11-3 | 1.7.27-4 | v3.5.25-251215 |
| v4.2.0 | v1.33.6 | 1.7.27-4 | v3.5.21-251117 |
| v4.2.1 | v1.33.7-1 | 1.7.29-4 | v3.5.25-251215 |
| v4.2.2 | v1.33.7-2 | 1.7.29-4 | v3.5.25-251215 |
| v4.2.3 | v1.33.7-3 | 1.7.29-4 | v3.5.27-260305 |
| v4.2.4 | v1.33.7-3 | 1.7.29-4 | v3.5.27-260305 |
| v4.2.5 | v1.33.7-4 | 1.7.29-4 | v3.5.28-260421 |
| v4.2.6 | v1.33.7-10 | 1.7.29-4 | v3.5.28-260421 |
| v4.3.0 | v1.34.5 | 2.2.1-5 | v3.5.28-260325 |
| v4.3.1 | v1.34.5-1 | 2.2.1-5 | v3.5.28-260421 |
| v4.3.2 | v1.34.5-3 | 2.2.1-5 | v3.5.28-260625 |
| v4.3.3 | v1.34.5-8 | 2.2.1-5 | v3.5.28-260818 |
| v4.4.0 | v1.35.6-acp.1 | 2.2.6-3 | v3.6.13-acp.0 |
| v4.4.1 | v1.35.6-acp.9 | 2.2.8-3 | v3.6.13-acp.2 |
| v4.5.0 | v1.36.4-acp.3 | 2.2.8-3 | v3.6.13-acp.5 |
Image Format by Provider
An Alauda OS image is published in different formats. Choose the format that matches your infrastructure provider when you download the image and upload it to the target platform:
For the virtual-machine providers, the format does not change the OS content — it only changes the packaging for the target platform. Select the entry on the download page that matches your provider.
Bare metal is packaged differently. Its download is a .tar archive of one OCI image layout that holds two images under the same tag, rather than a single bootable OS file. Push both images into the platform registry: for the installation of a global cluster, as described in OS Images in the Registry; for the hosts of workload clusters, as described in Prepare Alauda OS for Hosts:
The ISO that each host boots from is built on site by elemental-operator from the OS ISO image, and is not part of the download. See Create the Registration and the ISO.