Overview
Use the Install section to plan and complete an 4.5 installation.
The installation deploys Core and the required Aligned Extensions on the global cluster. Core provides the platform management plane, cluster management, users and roles, and Extension management frameworks. The required Aligned Extensions provide the Web Console and other platform-facing capabilities. For the platform architecture and definitions of global cluster and workload cluster, see Architecture and Glossary.
The Core Package and the Extension packages are separate downloads. Before starting the installer, copy all packages of ACP Common Aligned Extensions into the plugins/ directory of the extracted Core Package, as described in Download. After the platform installation, publish the Operators of ACP Common Aligned Extensions and the packages of ACP Common Agnostic Extensions with Violet; see Publish the Common Extensions. On Alauda OS, ACP CLI (ac) installs the global cluster from a temporary bootstrap cluster and installs the providers itself; see Installing the global Cluster.
Core installation does not support direct installation of the global cluster into an existing Kubernetes environment. On a non-Alauda OS, prepare new nodes that meet the hardware, network, storage, and OS requirements before you start installation. On Alauda OS, the installation provisions the global cluster nodes through an infrastructure provider; on Bare Metal you supply the hosts.
Installation Scope
The installation provides the platform management plane and the required Aligned Extensions. After the installation is verified, you can create or connect workload clusters and install additional Extensions according to your platform scenario.
The following work is outside this installation flow:
- Creating workload clusters.
- Connecting existing Kubernetes clusters.
- Uploading and installing ACP Common Agnostic Extensions.
- Installing optional Operators or Cluster Plugins.
- Configuring optional platform capabilities such as storage, monitoring, backup, registry, or identity integrations.
Choose an Installation Path
Choose the path by the operating system that the global cluster nodes run:
Installation Workflow
The installation follows this high-level path:
- Plan. Choose the deployment architecture, confirm decisions that cannot be changed safely after installation, and prepare the machines, addresses, domain name, and certificate that the installation needs. If required, read the Global Cluster Disaster Recovery page for your path before preparing resources: Alauda OS or non-Alauda OS. DR affects addresses, certificates, load balancing, registry selection, and the consistency of both installations.
- Prepare for installation. Complete the shared preparation that applies to your path:
- Download. Download the matching Core Package, ACP Common Aligned Extensions, and ACP Common Agnostic Extensions.
- Prepare the external platform image registry and upload the complete target-version payload.
- If you enable a host firewall on non-Alauda OS nodes, use the Communication Matrix to build the allow rules.
- Install the
globalcluster on one of the two paths:- Install on Alauda OS. Run a temporary bootstrap cluster on a bootstrap node, upload the provider packages, apply the provider-specific
globalmanifest, and trigger the platform installation. This path also covers the optional primary and standby deployment and the removal of the bootstrap cluster. - Install on Non-Alauda OS. Meet the requirements in Prepare Resources, Prerequisites, and Node Preprocessing. Then extract the Core Package, stage the required packages, start the installer, and complete the Web UI workflow. Use Installer Parameters while reviewing the values entered in the installer. If the installer stalls or validation fails, use Installation Troubleshooting.
- Install on Alauda OS. Run a temporary bootstrap cluster on a bootstrap node, upload the provider packages, apply the provider-specific
- Validation. Accept the installation only after the Web UI, Core, required Aligned Extensions, image source, artifacts, and Pods are healthy.
- Next Steps. Publish the Common Extensions, install the Product Docs plugin, and continue with scenario-specific configuration.
The Customer Portal is the official source for installation packages. For download requirements and package architecture options, see Download.
The Core Package does not contain the Aligned Extension packages. Download them separately and copy all of them into the plugins/ directory of the extracted Core Package before starting the installer; see Download.