#Download

Before installation, download the Core Package and the required Aligned Extension packages separately from the Customer Portal.

#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.

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

#Download the Installation Packages

1. Download the 4.4 Core Package that matches your target architecture.
2. Download Common ACP Extensions for the same version and architecture. The Violet CLI is the recommended method because it can locate and download the scenario packages directly.

#Download with Violet CLI (Recommended)

Install Violet v4.2.13 or later, run violet version to verify the version, and use violet ac login to log in to the Customer Portal. For installation and login instructions, see Download Packages.

Set <target-platform-version> to the exact ACP Distribution Version of the Core Package, such as v4.4.0. Set <arch> to amd64, arm64, or hybrid to match the Core Package. List the scenarios first, and then download Common ACP Extensions:

violet ac scenarios --arch=<arch> --platformVersion=<target-platform-version>
violet ac download-app --arch=<arch> --platformVersion=<target-platform-version> --scenario="Common ACP Extensions"

Confirm that Common ACP Extensions appears in the scenario list before downloading it.

#Download from the Customer Portal

As an alternative to Violet, in the Customer Portal, go to Marketplace > Batch Download > Install. On the page, select the Core Package version from Your ACP Version, select the matching Architecture, select Common ACP Extensions from Scenarios, and download the packages.

#Required Aligned Extensions

Copy the packages for the following applications into the plugins/ directory of the extracted Core Package:

• Alauda Container Platform Web Console
• Alauda Container Platform Web Console Central
• Alauda Container Platform Marketplace Web Console
• Alauda Container Platform Helm Application Catalog
• Alauda Container Platform Observability Essentials
• Alauda Container Platform Essentials
• Alauda Container Platform Cluster Essentials
• Alauda Container Platform GatewayAPI Plugin

Do not copy other packages from Common ACP Extensions into the extracted Core Package's plugins/ directory. Install those Extensions after the platform installation by following Extend.

#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, and use Extension packages that match the Core Package architecture.

#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