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.
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.
TOC
Choose a Deployment ArchitecturePrepare ResourcesMachinesNodes of theglobal ClusterInstallation MachineNetworkAddresses, Domain Name, and CertificatePackages and Image RegistryConfirm Install-Time DecisionsRead Before You InstallChoose a Deployment Architecture
Choose the architecture that matches your business scenario, management model, workload placement, resource planning, and isolation requirements.
For the nodes that each architecture needs, see Nodes of the global Cluster.
Prepare Resources
Prepare the following resources before you start the installation. The pages of your installation path add the details that apply only to that path.
Machines
Nodes of the global Cluster
The following sizes apply on both installation paths. They cover only the global cluster itself. Extensions and other components that you deploy on it need additional resources; see the documentation of each component.
On ARM nodes, such as Kunpeng 920, use twice the x86 configuration, and at least 1.5 times. For example, where x86 needs 8 cores and 16 GB, use 16 cores and 32 GB on ARM, and at least 12 cores and 24 GB.
For the disks of every node, see Disk Configuration.
How you provide the nodes depends on the installation path:
- Alauda OS on Bare Metal: provide one physical host for each node.
- Alauda OS on Huawei DCS, VMware vSphere, or Huawei Cloud Stack: the provider creates the nodes as virtual machines. Make sure that the platform has the capacity for them, and prepare a static IPv4 address and a hostname for each node. The disks of each node are declared in
install-config.yaml. - Non-Alauda OS: prepare the nodes yourself, as described in Node Preprocessing.
Installation Machine
- Alauda OS: prepare a bootstrap node. It is a temporary machine that runs ACP CLI (ac) and, during the installation, the bootstrap cluster. It does not join the
globalcluster. For its size, see Bootstrap Node. A disaster recovery pair needs one bootstrap node on each side. - Non-Alauda OS: you do not need a separate machine. You extract the Core Package and start the installer on one of the control plane nodes, and that node becomes the first control plane node of the
globalcluster.
Network
Insufficient bandwidth can significantly slow down data queries.
Addresses, Domain Name, and Certificate
- A control plane endpoint for the Kubernetes API: an external load balancer or a Self-built VIP. A Self-built VIP must be an IP address, not a domain name. See Plan the Control Plane Endpoint for Alauda OS, or Network for a non-Alauda OS.
- A domain name for the platform access address. Provide one by default, and make sure that it resolves before the installation. The platform access address uses the VIP of the control plane endpoint: it is a domain name that resolves to that VIP, or the VIP itself. You do not need a second VIP. Disaster recovery requires a domain name, and so does IPv6 access on a non-Alauda OS.
- An External VIP, only if some workload clusters cannot reach the platform access address, for example because they run in another network in a hybrid cloud. Prepare a VIP that they can reach, and configure it on the load balancer like the platform access address; see Platform Access Address and
globalVIP. On Alauda OS, list it inglobal.platform.extraAddresses; see Installation Reference. On a non-Alauda OS, enter it in the installer; see Installer Parameters. Prepare other access addresses, for example for an internal and an external network, in the same way. - Your own certificate, only if you want one. If browsers must trust the platform access address, prepare a certificate issued for it, with its private key. Otherwise, skip this: the platform generates a self-signed certificate. For disaster recovery, the certificate is required. It must cover the domain name and be the same on both sides. Self-signed certificates are not supported.
Packages and Image Registry
- The installation packages: the Core Package, ACP Common Aligned Extensions, and ACP Common Agnostic Extensions, for the same version and CPU architecture. See Download.
- An external platform image registry that every node can reach, with the payload of the target version uploaded. See Prepare an External Platform Image Registry.
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.
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,
ACP Common Aligned Extensions, andACP Common Agnostic Extensionsseparately, and verify that their version and architecture match. - Prepare an External Platform Image Registry: Upload the complete target-version Core and Extension payload before starting the installer.
For a non-Alauda OS:
- Prerequisites: Meet the network and load balancer requirements that apply only to a non-Alauda OS.
- Node Preprocessing: Check and prepare each node before installation.
- Global Cluster Disaster Recovery: Plan primary and standby
globalclusters 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
globalcluster with ACP CLI (ac) from the page for your provider. - Create a Global Cluster Disaster Recovery Pair: Plan primary and standby
globalclusters if disaster recovery is required.