Plan

Before you start the installation, choose the deployment architecture and confirm the installation settings that affect later operations. The installation paths are Install on Alauda OS and Install on Non-Alauda OS. Where a decision applies to only one path, this page says so.

INFO

The installation deploys the global cluster on new nodes: nodes that you prepare on a non-Alauda OS, or Alauda OS nodes that the installation provisions through an infrastructure provider. It does not support direct installation of the global cluster into an existing Kubernetes environment.

Choose a Deployment Architecture

Choose the architecture that matches your business scenario, management model, workload placement, resource planning, and isolation requirements.

Architecture	Use when	Planning notes
Multi-Cluster	You need one `global` cluster to manage multiple workload clusters.	Avoid running non-platform workloads on the `global` cluster. Plan resources for the expected number of managed workload clusters.
Single Cluster	You intentionally use one cluster for platform components and application workloads.	Single Cluster supports production use when it fits the business scenario. Because the `global` cluster also runs application workloads, plan resources and platform/workload isolation before installation.
Single Node	You need a test or proof-of-concept environment.	Do not use Single Node for production. On Alauda OS, whether a single control plane node is possible depends on the provider; see the following list.

On Alauda OS, a single control plane node depends on the provider:

VMware vSphere: not supported. A KubeadmControlPlane needs at least three replicas. See Provider Requirements.
Bare Metal: not supported. Provision at least three control plane replicas. See Step 3: Create the Control-Plane Cluster Resources.
Huawei Cloud Stack: supported for creation only, not for upgrade. See Create a Cluster on Huawei Cloud Stack.

For resource requirements and sizing guidance on a non-Alauda OS, see Prerequisites. For Alauda OS, see Common Prerequisites and, for global cluster sizing, Evaluating Resources for Global Cluster. Bootstrap Node Requirements apply to the temporary bootstrap node only.

Confirm Install-Time Decisions

Confirm the following decisions before you start the installation. The last two columns link to the page that documents each decision on each path.

Decision	What to confirm	Non-Alauda OS	Alauda OS
Installation packages	Choose an x86, ARM, or hybrid Core Package and download the required Aligned Extension packages for the same version and architecture. On Alauda OS, also prepare the provider packages and the Alauda OS image or VM template.	Download	Download and Common Prerequisites
Cluster network protocol	On a non-Alauda OS, choose IPv4, IPv6, or dual stack before starting the installer. On Alauda OS, plan the Pod and Service CIDR ranges.	Installing	Common Prerequisites
Cluster Endpoint and Platform Access Address	Prepare the access addresses that cluster components, administrators, and users will use.	Prerequisites and Installer Parameters	Common Prerequisites and Plan the Control Plane Endpoint
Load balancing	Decide whether to use an external load balancer or Self-built VIP. On Alauda OS, the endpoint modes available depend on the provider.	Prerequisites and LoadBalancer Forwarding Rules	Plan the Control Plane Endpoint
Certificates	Decide whether to use installer-generated self-signed certificates or trusted certificates that you provide.	Prerequisites and Installer Parameters	Trigger the Platform Installation
Platform image source	Decide whether to use the platform built-in Registry or a customer-managed external platform image registry. For new production deployments, use an external registry when it meets the documented availability and lifecycle requirements.	Prepare an External Platform Image Registry and Installer Parameters	Prepare an External Platform Image Registry and Common Prerequisites
Nodes	Confirm node names, node roles, and whether platform node isolation is required.	Node Preprocessing and Installer Parameters	Common Prerequisites
Global Cluster Disaster Recovery	Decide whether your environment requires primary and standby `global` clusters.	Global Cluster Disaster Recovery	Global Cluster Disaster Recovery and Optional Disaster Recovery Deployment

If you plan to use Global Cluster Disaster Recovery, read the Global Cluster Disaster Recovery page for your installation path before installing Core. Disaster recovery planning affects domain names, VIPs, certificates, load balancer rules, image registry choices, package architecture, and installation parameter consistency.

Read Before You Install

Use the following pages as the source of truth before you start the installation.

For both installation paths:

Disk Configuration Requirements: Confirm disk capacity and performance requirements.
Download: Download the Core Package and Common ACP Extensions separately, and verify that their version and architecture match.
Prepare an External Platform Image Registry: If selected, upload the complete target-version Core and Extension payload before starting the installer.

For a non-Alauda OS:

Prerequisites: Prepare resource, network, and storage requirements.
Node Preprocessing: Check and prepare each node before installation.
Global Cluster Disaster Recovery: Plan primary and standby global clusters if disaster recovery is required.
Installing: Upload the Core Package, stage required packages, and start the installer.
Installer Parameters: Configure the installation choices in the Web UI.

For Alauda OS:

Installing the global Cluster: Meet the common prerequisites and bootstrap node requirements, then install the global cluster through the bootstrap cluster for your provider.
Global Cluster Disaster Recovery: Plan primary and standby global clusters if disaster recovery is required.

#Plan

#TOC

#Choose a Deployment Architecture

#Confirm Install-Time Decisions

#Read Before You Install

Plan

TOC

Choose a Deployment Architecture

Confirm Install-Time Decisions

Read Before You Install