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.

Install 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. A global cluster installed with ac already runs the Cluster Bootstrap Provider and the provider of its own platform. 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:

  1. Download: Download the packages from the Customer Portal. For 4.5, the providers are in ACP Common Aligned Extensions. See Download.
  2. Upload: Upload the packages to the platform with violet push. See Upload Packages.
  3. Install: Install the packages as cluster plugins on the global cluster. See Cluster Plugin.

For the packages of each provider, see:

Configure Infrastructure Resources

The infrastructure each provider needs is on its Prerequisites page: Bare Metal, Huawei DCS, Huawei Cloud Stack, and VMware vSphere. ac renders the provider's IP pools and machine templates from install-config.yaml.

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: ac reads its address from the registry key of the public-registry-credential Secret in cpaas-system on global. 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.