Prepare
Complete the following preparation before you create a workload cluster on Alauda OS. It applies to every provider. For the list of supported providers, see Supported Providers.
TOC
Install the Infrastructure ProviderConfigure Infrastructure ResourcesPlan the Control Plane EndpointChoose the Image RegistryInstall the Infrastructure Provider
After the global cluster is installed, and before you create a workload cluster on Bare Metal, Huawei DCS, Huawei Cloud Stack, or VMware vSphere, upload and install the infrastructure provider for that IaaS platform on the global cluster. This applies regardless of which IaaS platform the global cluster itself runs on. In a DR pair, do this on both global clusters.
In addition to the infrastructure provider, the following component is required for every provider:
- Alauda Container Platform Cluster Bootstrap Provider: Handles Kubernetes bootstrap and control plane management
Install both as follows:
- Download: Download the packages from the Customer Portal. For 4.5, the providers are listed under Common ACP Extensions. See Download.
- Upload: Upload the packages to the platform with
violet push. See Upload Packages. - Install: Install the packages as cluster plugins on the
globalcluster. See Cluster Plugin.
For the packages and verification steps of each provider, see:
Configure Infrastructure Resources
Before creating clusters, configure the infrastructure resources that the provider requires:
- Cloud Credentials: Store IaaS platform access information
- IP Pools: Define network configurations for cluster nodes
- Machine Templates: Specify virtual machine specifications
- Network Inventory and Load Balancer Plans: Prepare subnet inventories and API server access addresses when the provider requires them
Bare Metal has no separate infrastructure resource page. Its host preparation is part of Install the Bare Metal Provider and Create a Cluster on Bare Metal.
Plan the Control Plane Endpoint
Every cluster needs a stable endpoint for the Kubernetes API, and the endpoint mode must be selected before the cluster is created. See Plan the Control Plane Endpoint.
Choose the Image Registry
By default, a workload cluster uses the image registry of the global cluster. A cluster can instead be bound to a dedicated registry, but only when it is created. See Choose the Image Registry for a Workload Cluster.