Download

Before installation, download the Core Package, ACP Common Aligned Extensions, and ACP Common Agnostic Extensions 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.5 Core Package that matches your target architecture.
  2. Download ACP Common Aligned Extensions for the same version and architecture.
  3. Download ACP Common Agnostic Extensions for the same version and architecture.
  4. If you install the global cluster on Alauda OS, also download the Alauda OS image for your node architecture and provider. See Downloading Alauda OS.

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. Run Violet on a machine that has access to the Customer Portal, and copy the packages to the installation environment. For installation and login instructions, see Download Packages; for the address and access token to use, see Addresses and Credentials.

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

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

Confirm that both scenarios appear in the scenario list before downloading them.

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 ACP Common Aligned Extensions and ACP Common Agnostic Extensions from Scenarios, and download the packages.

Copy the Packages into plugins/

The Core Package contains Core artifacts only. After you extract it, copy all packages of ACP Common Aligned Extensions into its plugins/ directory before you start the installation.

Do not copy the packages of ACP Common Agnostic Extensions there. Publish them with Violet after the installation, together with the Operators of ACP Common Aligned Extensions; see Publish the Common Extensions.

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. Extract the newly downloaded hybrid Core Package on an execution host, as described in Prepare the Execution Host. Do not use a node of the global cluster.

  2. Log in with ac login and select the global cluster. Then, from the installer/ directory of the package, use the included upgrade.sh script to synchronize the multi-architecture images to your image registry:

    ac config use-cluster global
    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