Alauda Container Platform

Download

Before installation, download the Core Package from the Customer Portal.

TOC

About the Customer PortalChoose a Package ArchitectureMigrating from Single-Architecture to Hybrid

About the Customer Portal

The Customer Portal is the official service and delivery portal for product resources. Use it to obtain verified software packages and official technical guidance for installation, upgrade, and maintenance activities.

The Customer Portal provides access to the following resources:

  • Product downloads, including installation, upgrade, and extension packages.
  • Product documentation and technical guidance.
  • Support resources for submitting, tracking, and managing support requests.
  • Marketplace packages for extending platform capabilities.
  • License-related resources for deployment and maintenance planning.

Use an authorized account to download the package required for your environment. If you do not have a registered account, contact technical support.

INFO

Starting from v4.1, if you download both the Core Package and the Extensions Packages, you must complete the installation of the Core Package before uploading and installing Extensions Packages.

For customer delivery and production environments, use the package versions and documentation published on the Customer Portal as the official deployment and maintenance baseline.

Choose a Package Architecture

Packages are available for x86, ARM, and hybrid architectures. The hybrid package includes images for both x86 and ARM, resulting in a larger package size. Select the package that best matches your environment.

Migrating from Single-Architecture to Hybrid

If you initially installed with an x86 or ARM Core Package but later need to support another architecture, you must re-download the hybrid Core Package and perform the following steps:

  1. Upload the newly downloaded hybrid Core Package to any control plane node of the global cluster.

  2. Extract the package and use the included upgrade.sh script to synchronize the multi-architecture images to your image registry:

    bash upgrade.sh --only-sync-image=true

  3. After the script completes, check the cluster.platform.tkestack.io resource to verify whether the label cpaas.io/node-arch-constraint exists. If it does, you must remove it:

    kubectl get cluster.platform.tkestack.io global -oyaml | grep cpaas.io/node-arch-constraint
# If there is output, edit the resource to remove the label; otherwise, you can skip this step.
kubectl edit cluster.platform.tkestack.io global   ### Edit the labels field and delete cpaas.io/node-arch-constraint