After installing the Bare Metal Orchestrator bundle, you must configure the Global Controller site. You must use the Bare Metal Orchestrator CLI to create the Global Controller site.
- You require the Global Controller node name to perform this procedure, run:
installer@installer-virtual-machine:~/mw_bundle/samples/sites$ kubectl get nodes
- Manually copy the sample files from the mw_bundle/samples directory on the Global Controller (CP1) to a directory called /home/dell. For high availability (HA) deployments, copy the sample files to the servers hosting the two Load Balancers.
- The automatically created kubeconfig file for the initial admin user references the IP address of the Global Controller (CP1) by default. The Global Controller IP address is used for a single node deployment. For HA deployments, you must manually change the Global Controller IP address in the kubeconfig file to the virtual IP (VIP) address of the Load Balancers. For AWS deployments, you must manually change the Global Controller (CP1) IP address in the kubeconfig file to the DNS name of the AWS load balancer.
- A user account with passwordless sudo privileges configured, see Enable and disable passwordless sudo privileges.
This procedure describes how to edit the mw_bundle/samples/sites/gc.yaml file to include the Common Language Location Identifier (CLLI) information for the Global Controller site, and then create the site.
During this procedure, you must generate a valid token for the initial admin user that was created for the Bare Metal Orchestrator installation and access the initial admin user's kubeconfig file.
To configure the Global Controller site using the Bare Metal Orchestrator CLI, do the following:
Verify that all the Bare Metal Orchestrator cluster nodes were created, see Viewing nodes.