Alauda Container Platform

Pre-Upgrade Preparation

Supported upgrade paths:

  • From 4.0 → 4.3
  • From 4.1 → 4.3
  • From 4.2 → 4.3

Before starting, ensure your current platform version is within the supported upgrade range.

TOC

Important NotesDownload the Packages for Offline Environments

Important Notes

  • Ensure the directory /cpaas/minio on the control plane nodes of global cluster has at least 120 GB of free disk space.
  • Before upgrading the global tier to ACP 4.3, all workload clusters must remain within the ACP 4.3 Compatible Versions documented in Kubernetes Support Matrix.
  • If any workload cluster is outside that compatible range, upgrade that workload cluster first until it enters the ACP 4.3 compatible range before upgrading the global tier.
  • A workload cluster can be upgraded only to a Distribution Version that the global tier has already reached.

Download the Packages for Offline Environments

From the Customer Portal, download the Core Package.

If you want to upgrade cluster Extensions during the upgrade, follow these steps:

  1. Navigate to the CLI Tools section in the Customer Portal and download the violet tool. This tool is required for uploading Extensions. For more information about violet, see Upload Packages.

  2. On any machine with network access to the platform endpoint, run violet list to list the extensions in the current environment and export the output to ./apps.yaml.

    violet list \
  --platform-address "https://<your-platform-domain>" \
  --platform-username "<platform_user>" \
  --platform-password "<platform_password>" \
  --output-file "./apps.yaml"
    WARNING

    Passing --platform-password on the command line records the password in shell history and process listings (ps aux). If your environment supports reading the password from stdin or an environment variable, prefer that path; run violet list --help to see available alternatives.

  3. Import the exported apps.yaml file into the Customer Portal to align the extension list.

WARNING

If you are upgrading from ACP 4.0 to ACP 4.3 and Build of TopoLVM is installed on any target clusters, upload the TopoLVM package to those clusters before you proceed with the upgrade. This step is not required when upgrading from ACP 4.1 or ACP 4.2. You can specify multiple target clusters in --clusters, separated by commas.

violet push <path/to/directory/only_put_topolvm_plugin_here> \
  --target-catalog-source "platform" \
  --platform-address "https://example.com" \
  --platform-username "<platform_user>" \
  --platform-password "<platform_password>" \
  --clusters "cluster-a,cluster-b"
WARNING

Starting with v4.2, we introduced a new plugin named Alauda Container Platform Log Essentials. If you previously installed the log storage plugin, you also have to upload that plugin before starting the upgrade.