Installing
This section describes how to install Core and the required Aligned Extensions, and deploy the global cluster.
This installation path applies to clusters running on a traditional operating system. If your environment uses Alauda OS, see Installing the global Cluster on Immutable Infrastructure instead.
Before starting the installation, ensure that you have completed the prerequisite checks, downloaded and verified the Core Package and required Aligned Extension packages, completed node preprocessing, and finished the other preparation work. If you selected an external platform image registry, its complete target-version payload must already be available before you run setup.sh.
TOC
ProcessValidate the InstallationInstaller Parameter ReferenceInstallation TroubleshootingAdditional ResourcesProcess
Upload and Extract Installation Package
Upload the Core Package installation package to any machine of the global cluster control plane nodes, and extract it according to the following command:
- This machine will become the first control plane node after the
globalcluster installation is complete. - After the Core Package is extracted, at least 100GB of disk space is required. Please ensure sufficient storage resources.
- The Core Package does not contain the required Aligned Extension packages. Prepare them separately as described in Download.
Prepare the Required Aligned Extension Packages
Copy each of the eight packages listed in Required Aligned Extensions into the plugins/ directory of the extracted Core Package. Run the following command once for each package:
Confirm that the directory contains the eight required packages before starting the installer:
Do not copy other packages from Common ACP Extensions into this directory. The installer processes only the packages that you manually place in plugins/; it does not download packages from the Customer Portal.
Start the Installer
Choose the command that matches the platform image source. After the installer starts successfully, the terminal outputs the web console access address.
After waiting for about 5 minutes, you can use a browser on your PC to access the web console provided by the installer.
For the platform built-in Registry:
For an external registry that permits anonymous pull:
For an authenticated external registry, provide the pull username and password together. The pull account used by setup.sh can be different from the push account used to upload the payload:
The registry address must use the form <host-or-IP>[:port] without http:// or https://. Do not provide only one of --username and --password.
Ensure that the IP address and port 8080 of the node where the installer is located can be accessed normally, so that the web console provided by the installer can be accessed smoothly after the installer starts successfully.
IP Family
If you plan to create a global cluster with Single-stack Network IPv6, you must explicitly specify --ip-family ipv6 when starting the installer. Without this parameter, the global cluster created by the installer will support Single-stack Network IPv4 and Dual-stack Network by default.
Parameter Configuration
Configure the installation in the Web UI, review every value, and then confirm the installation. Use Installer Parameters for the field-by-field reference.
Validate the Installation
After the installer reports that the installation is complete, validate Core and the required Aligned Extensions before continuing with post-install tasks. For the checklist and commands, see Validation.
Installer Parameter Reference
For the detailed field reference, see Installer Parameters.
Installation Troubleshooting
For installer stalls, failed resources, image-pull failures, missing artifacts, and cleanup, see Installation Troubleshooting.