1. Documentation
×

Installing a cluster

You can install a cluster after setting up the environment for an OKD installation. Ensure you have completed the prerequisites before installing a cluster.

Cleaning up previous installations

You must remove the artifacts from any failed deployment attempt before trying to deploy OKD again.

Procedure

  1. Power off all bare-metal nodes before installing the OKD cluster by using the following command:

    $ ipmitool -I lanplus -U <user> -P <password> -H <management_server_ip> power off

  2. Remove all old bootstrap resources if any remain from an earlier deployment attempt by using the following script:

    for i in $(sudo virsh list | tail -n +3 | grep bootstrap | awk {'print $2'});
do
  sudo virsh destroy $i;
  sudo virsh undefine $i;
  sudo virsh vol-delete $i --pool $i;
  sudo virsh vol-delete $i.ign --pool $i;
  sudo virsh pool-destroy $i;
  sudo virsh pool-undefine $i;
done

  3. Delete the artifacts that the earlier installation generated by using the following command:

    $ cd ; /bin/rm -rf auth/ bootstrap.ign master.ign worker.ign metadata.json \
.openshift_install.log .openshift_install_state.json

  4. Re-create the OKD manifests by using the following command:

    $ ./openshift-baremetal-install --dir ~/clusterconfigs create manifests

Deploying the cluster via the OKD installer

You can deploy the cluster by running the OKD installer.

Procedure

  • Run the OKD installer:

    $ ./openshift-baremetal-install --dir ~/clusterconfigs --log-level debug create cluster

Following the progress of the installation

During the deployment process, you can check the installation’s overall status by issuing the tail command to the .openshift_install.log log file in the install directory folder.

Procedure

  • Track installation progress by running the following command:

    $ tail -f /path/to/install-dir/.openshift_install.log

Verifying static IP address configuration

Ensure that all required steps are complete and verify the network configuration is working properly.

If the DHCP reservation for a cluster node specifies an infinite lease, after the installer successfully provisions the node, the dispatcher script checks the node’s network configuration.

If the script determines that the network configuration contains an infinite DHCP lease, it creates a new connection by using the IP address of the DHCP lease as a static IP address.

The dispatcher script might run on successfully provisioned nodes while the provisioning of other nodes in the cluster is ongoing.
Procedure

  1. Check the network interface configuration on the node.

  2. Turn off the DHCP server and reboot the OKD node and ensure that the network configuration works properly.

Additional resources