OS Support Matrix
This document lists the versions of Kubernetes components included in different Alauda OS images.
CPU 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.
An ACP release can publish more than one image — one per architecture, and from ACP v4.4.0 more than one OS variant. Every image published for the same ACP release contains the component versions listed in that release's row below, so select the image by your node architecture and by the file format your provider requires. See Image Format by Provider.
Version Mapping
Huawei DCS provider pairing
For Huawei DCS clusters that use the Alauda OS image published for ACP v4.3.2 or later, including ACP v4.4.0 and later, use DCS Provider v1.0.21 or later. Do not pair DCS Provider v1.0.21 or later with an Alauda OS image published for a release earlier than ACP v4.3.2. DCS Self-built VIP additionally requires DCS Provider v1.0.22 or later and ACP v4.4 or later. For the complete requirement, see Alauda OS and Provider Compatibility.
The kube-ovn (chart) column contains the Helm chart version that tracks the ACP release line (for example, ACP v4.2.2 ships chart v4.2.24). It is not the Kube-OVN component (binary) version such as v1.14.x or v1.15.x.
Chart versions earlier than v4.4 use acp/chart-cpaas-kube-ovn; chart v4.4 and later use acp/chart-kube-ovn. Use the matrix value with the provider-version-specific Kube-OVN upgrade procedure. Do not assume that every provider version supports both chart sources.
Image Format by Provider
An Alauda OS image is published in different file formats. Choose the format that matches your infrastructure provider when you download the image and upload it to the target platform:
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.