Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Archive > Design Guide—Dell Ready Stack for Red Hat OpenShift Container Platform 4.3 CSI Attached Storage > Deployment process
Dell Technologies has simplified the process of bootstrapping the OpenShift Container Platform 4.3 cluster. To use the simplified process, ensure that:
The deployment procedure begins with initial switch provisioning. See the OpenShift 4.3 Deployment Guide for sample switch configurations.
This step enables preparation and installation of the CSAH node, involving:
Dell Technologies has generated Ansible playbooks that fully prepare the CSAH node. Before the installation of the OpenShift Container Platform 4.3 cluster begins, the Ansible playbook sets up a PXE server, DHCP server, DNS server, and HTTP server. The playbook also creates ignition files to drive installation of the bootstrap, master, and worker nodes and it configures HAProxy so that the installation infrastructure is ready for the next step. The playbook presents a list of node types that must be deployed in top-down order.
Note: For enterprise sites, consider deploying appropriately hardened DHCP and DNS servers. Similarly, consider using resilient multiple-node HAProxy configuration. The Ansible playbook for this design deploys a single HAProxy instance. The CSAH Ansible playbooks in this guide are provided for reference only at the implementation stage.
The Ansible playbook creates an installconfig file that is used to control deployment of the bootstrap node. For more information, see the Dell EMC Ready Stack: Red Hat OpenShift Container Platform 4.3 Deployment Guide. An ignition configuration control file starts the bootstrap node, as shown in the following figure:
Figure 2. OpenShift Container Platform 4.3 installation workflow: Creating the bootstrap, master, and worker nodes
Note: An installation that is driven by ignition configuration generates security certificates that expire after 24 hours. You must install the cluster before the certificates expire, and the cluster must operate in a viable (nondegraded) state so that the first certificate rotation can be completed.
The cluster bootstrapping process includes the following phases:
The master node (control plane) now drives creation and instantiation of the worker nodes.
The cluster is now viable and can be placed into service in readiness for Day 2 operations. You can expand the cluster by adding worker nodes. See the OpenShift 4.3 Deployment Guide for adding additional worker nodes.