Prerequisites

First prepare what every installation needs, as listed in Plan: the nodes and their sizes and the network in Prepare Resources, and the addresses and domain name, your own certificate if you use one, the installation packages, and the external platform image registry in Confirm Install-Time Decisions. This page lists the additional requirements on a non-Alauda OS.

INFO
  1. The platform currently does not support direct installation of the global cluster in an existing Kubernetes environment. If your environment already has a Kubernetes cluster, please back up your data and clean the environment before installation.
  2. If you plan to use global Cluster Disaster Recovery, please first read global Cluster Disaster Recovery.
  3. Make sure all of the new nodes meet the Nodes Requirements.

First Control Plane Node

You start the installer on one of the control plane nodes, and that node becomes the first control plane node of the global cluster. In addition to the disks in Disk Configuration, this node needs at least 120 GB, and 250 GB is recommended, for the extracted Core Package and the Extension packages that you copy into it. The actual size depends on the Extensions that you install, so plan more space if you expect to add components later.

Network

If a hardware LoadBalancer is available in your environment, it is recommended to use it. If not, you can enable Self-built VIP, which provides software load balancing using keepalived. For the network requirements of Self-built VIP, see Self-built VIP.

In the installer, enter the global VIP as the Cluster Endpoint. The Cluster Endpoint does not take a domain name. The API server certificate is issued by the cluster's own CA, so a domain name on the cluster endpoint cannot carry a customer-issued certificate.

TypeRequirement Description
Network PolicyAllow the network flows listed in Communication Matrix, and configure the load balancer as described in LoadBalancer Forwarding Rules.
IP Address RangeThe global cluster nodes should avoid using the 172.17-18 network segment. If it has been used, please adjust the nerdctl configuration (add the bip parameter) to avoid conflicts.

LoadBalancer Forwarding Rules

Configure the load balancer of the global cluster to forward the ports marked in the Forward on load balancer column of Platform Access Address and global VIP to all control plane nodes. That section also covers a custom HTTPS port, HTTP access, and global disaster recovery. The platform built-in Registry port applies only to a global cluster upgraded from an earlier version that still uses that registry.

External Platform Image Registry

A new installation of 4.5 or later requires a customer-managed external platform image registry.

Before running setup.sh, complete Prepare an External Platform Image Registry. That page defines the required address, network access, storage, and push and pull permissions; separates those requirements from production recommendations; and explains how to upload the complete target-version payload.