Alauda Container Platform
  • English

    • 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 required Aligned Extension packages are separate downloads. Before starting the installer, copy the eight required Extension packages listed in Download into the plugins/ directory of the extracted Core Package. Other Extensions are installed after the platform installation through the Extend workflow. On Alauda OS, the installation also uploads the Cluster Bootstrap Provider and infrastructure provider packages to a temporary bootstrap cluster; see Installing the global Cluster.

    INFO

    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.

    TOC

    Installation ScopeChoose an Installation PathInstallation WorkflowRelated Documentation

    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 Extensions other than the eight required Aligned 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:

    Node operating systemInstallation path
    Alauda OS, provisioned through an infrastructure provider on Huawei DCS, VMware vSphere, Huawei Cloud Stack, or Bare Metal.Install on Alauda OS
    A non-Alauda OS such as Ubuntu or RHEL, on nodes that you prepare.Install on Non-Alauda OS

    Installation Workflow

    The installation follows this high-level path:

    1. Plan. Choose the deployment architecture and confirm decisions that cannot be changed safely after installation. 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.
    2. Prepare for installation. Complete the shared preparation that applies to your path:
    3. Install the global cluster 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 global manifest, 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 hardware, storage, network, and node requirements in 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.
    4. Validation. Accept the installation only after the Web UI, Core, required Aligned Extensions, image source, artifacts, and Pods are healthy.
    5. Next Steps. 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.

    Separate Downloads

    The Core Package does not contain the required Aligned Extension packages. Download them separately and manually copy only the eight packages listed in Download into the plugins/ directory of the extracted Core Package before starting the installer.