Plan

This page is the entry point for every installation of , on both installation paths. It helps you choose the deployment architecture, prepare the resources, and confirm the decisions that you cannot change safely after the installation. On Alauda OS, continue with Typical Installation Scenarios for the standard sizes and steps of the architecture that you choose.

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.

ArchitectureUse whenPlanning notes
Multi-ClusterYou need one global cluster to manage multiple workload clusters.Plan resources for the expected number of managed clusters, and run no business workloads on the global cluster.
Single ClusterYou intentionally use one cluster for platform components and business workloads, including in production.Plan resources and platform/workload isolation before the installation, because the global cluster also runs business workloads.
Single NodeYou need a test or proof-of-concept environment.Do not use it for production, because a cluster with a single control plane node cannot be upgraded.

Prepare Resources

Prepare the following machines and network 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 and cover only the global cluster itself. Extensions and other components that you deploy on it need additional resources.

ArchitectureNodesCPU and memory of each node
Multi-ClusterThree control plane nodes, and more as the scale growsDepends on the number of managed clusters.
Single ClusterThree control plane nodesAt least 8 cores and 16 GB, and more as the number of worker nodes grows.
Single NodeOne nodeAt least 12 cores and 24 GB.
  • For the tiers, see Evaluating Resources for Global Cluster.
  • 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, and the disks of each node are declared in install-config.yaml. Make sure that the platform has the capacity for them, and prepare a static IPv4 address and a hostname for each node.
  • Non-Alauda OS: prepare the nodes yourself, as described in Node Preprocessing.

Installation Machine

  • Alauda OS: prepare a bootstrap node, one on each side for disaster recovery. It is a temporary machine that runs ACP CLI (ac) and the bootstrap cluster, and it does not join the global cluster. For its size, see Bootstrap Node.
  • Non-Alauda OS: you do not need a separate machine. You start the installer on one of the control plane nodes, and that node becomes the first control plane node of the global cluster. For the extra disk space that this node needs, see First Control Plane Node.

Network

Network pathBandwidthLatency
Within a clusterAt least 1 Gbps; 10 Gbps is recommendedAt most 10 ms
Between clustersAt least 100 Mbps; 1 Gbps is recommendedAt most 100 ms; 30 ms or less is recommended

Insufficient bandwidth can significantly slow down data queries.

Confirm Install-Time Decisions

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

DecisionWhat to decide and prepareNon-Alauda OSAlauda OS
Installation packagesDownload the Core Package, ACP Common Aligned Extensions, and ACP Common Agnostic Extensions for the same version and CPU architecture.DownloadDownload, Common Prerequisites
External platform image registryPrepare a registry that every node can reach, and upload the payload of the target version to it.Prepare an External Platform Image Registry, Installer ParametersPrepare an External Platform Image Registry, Common Prerequisites
Control plane endpointChoose an external load balancer or a Self-built VIP for the Kubernetes API.Network, LoadBalancer Forwarding RulesPlan the Control Plane Endpoint
Platform access addressPrepare a domain name that resolves to the VIP of the control plane endpoint before the installation.Installer ParametersCommon Prerequisites
External VIPPrepare one only if some workload clusters cannot reach the platform access address.Installer Parametersglobal.platform.extraAddresses in Installation Reference
CertificateProvide a trusted certificate and private key for the platform access address, or use the self-signed certificate that the platform generates.Installer Parametersglobal.platform.cert in Installation Reference
Cluster networkChoose IPv4, IPv6, or dual stack on a non-Alauda OS, and change the default CIDR ranges on Alauda OS only if they overlap the node network.Installingcluster.network in Installation Reference
NodesConfirm node names, node roles, and whether platform node isolation is required.Node Preprocessing, Installer ParametersInfra Nodes
Global Cluster Disaster RecoveryDecide whether your environment requires primary and standby global clusters.Global Cluster Disaster RecoveryCreate a Global Cluster Disaster Recovery Pair
  • Installation packages: on Alauda OS, also prepare the Alauda OS image or VM template.
  • External platform image registry: a new installation of 4.5 or later does not support the platform built-in Registry. Only a global cluster upgraded from an earlier version can keep using it.
  • Control plane endpoint: a Self-built VIP must be an IP address, not a domain name.
  • Platform access address: it is a domain name that resolves to the VIP of the control plane endpoint, or the VIP itself, so no second VIP is needed. Disaster recovery and IPv6 access on a non-Alauda OS require a domain name.
  • External VIP: configure it on the load balancer like the platform access address; see Platform Access Address and global VIP. Prepare other access addresses, for example for an internal and an external network, in the same way.
  • Certificate: disaster recovery requires a provided certificate that covers the domain name and is the same on both sides. Self-signed certificates are not supported for disaster recovery.

If you plan disaster recovery, read the page for your installation path before you install Core. Disaster recovery affects domain names, VIPs, certificates, load balancer rules, the image registry, the package architecture, and the consistency of the installation parameters.

Next Steps

Continue with the entry page of your installation path: