Create the global Cluster on VMware vSphere
TOC
PrerequisitesProcedure1. Writeinstall-config.yaml2. Create the Cluster3. Monitor the InstallationVerificationNext StepsPrerequisites
- You completed the common prerequisites and the VMware vSphere prerequisites.
- The Core Package is extracted on the bootstrap node, and its payload is in the external registry. See Prepare the Core Package and the Registry.
- For a disaster recovery pair, write both files as described in Create a Global Cluster Disaster Recovery Pair, then run this procedure on each side.
Procedure
1. Write install-config.yaml
Create an installation directory on the bootstrap node, for example /root/global-install, and write install-config.yaml in it. The commands on this page call this directory <install-dir>; see Installation Directory. Keep the file private (chmod 600 install-config.yaml), because it holds the passwords.
Copy the following template and fill in the placeholders. The numbered lines are specific to VMware vSphere and are described in the table below the template. For the other fields, see Common install-config.yaml Fields. For the objects that ac renders from this file, see Rendered Manifests.
If you give a datastore, folder, or port group as an inventory path, make sure that the path exists.
2. Create the Cluster
On the bootstrap node:
ac first checks the CPI image in the Core Package, the vCenter sign-in, and the vCenter objects named in install-config.yaml. If a check fails, nothing is changed, and the error names the first missing item. Make sure that an external load balancer is ready before you run create.
create returns when the installation is complete. If create stops, run the same command again. It skips the work that is already complete. See The create Command.
3. Monitor the Installation
From another terminal on the bootstrap node:
For the stages and common failures, see Troubleshooting. For VMware vSphere failures, see Troubleshooting on VMware vSphere.
Verification
When create returns, the installation is complete, but some platform components can take a few more minutes to become ready. Before you judge the result, wait for them as described in Additional Checks for Alauda OS. Then verify the platform as described in Validation, including its checks for Alauda OS.
Applies to: a Self-built VIP (cluster.network.loadBalancer.type: internal). Skip this check with an external load balancer.
Log in to a control plane node of the global cluster as the boot user (ssh boot@<control-plane-node-ip>). Use the private key that matches an SSH public key in cluster.sshKeys. Run curl with sudo, because only root can read the cluster CA file:
Continue when it prints ok. Otherwise, see Troubleshooting on VMware vSphere.
Next Steps
- A disaster recovery pair: continue with Install the Primary and the Standby.
- Create a Cluster on VMware vSphere. The
globalcluster already runs the VMware vSphere provider. - To create workload clusters on other infrastructure, install that provider as described in Prepare.