The steps below guide you through the post-installation steps of OpenShift. It assumes that the OpenShift masters and workers are in Ready state.
The following script will clean up the PXE links and rebuild the known_hosts file.
/ocp_install/scripts/post_install.sh
Amongst others, the script may opt the cluster out from remote health checking. Applying these changes to all nodes will take some time. To wait for the cluster operators to become ready, run the following:
/ocp_install/scripts/wait_co_ready.sh
After the workers have been deployed, you may no longer need the DHCP server that is running on the bastion node. To avoid any conflicts with other activities on the VMWare infrastructure, you can now disable the DHCP service within dnsmasq.
/ocp_install/scripts/disable_dhcp.sh
IMPORTANT: After completing the OpenShift 4.x installation, ensure that you keep the cluster running for at least 24 hours. This is required to renew the temporary control plane certificates. If you shut down the cluster nodes before the control plane certificates are renewed and they expire while the cluster is down, you will not be able to access OpenShift.
You can now access OpenShift by editing your /etc/hosts file. See Access OpenShift for more details.
You can now continue with the installation of one of the Cloud Paks.