About This Architecture

OpenShift 4.20.13 cluster deployed on VMware vSphere with a three-node control plane (ocpqa-master-0/1/2) and three-node compute plane (ocpqa-worker-0/1/2) running RHCOS, orchestrated through vCenter Server Appliance across ESXi hosts with vSAN/NFS datastore backing. Network traffic flows from Internet through Firewall and Load Balancer (VIPs) to the cluster, with DNS/DHCP and Bastion Host providing infrastructure support. The ocpqa-bootstrap node temporarily coordinates initial cluster formation and etcd quorum synchronization across control plane nodes. This architecture demonstrates enterprise-grade Kubernetes deployment patterns with high availability, network segmentation (DMZ, LAN, WAN zones), and vSphere resource pooling for production QA environments. Fork this diagram on Diagrams.so to customize node counts, storage backends, or network policies for your OpenShift deployment. The design isolates control and compute planes while maintaining secure external access through load-balanced VIPs.

People also ask

How do you deploy OpenShift 4.20 on VMware vSphere with high availability and proper network segmentation?

This diagram shows a production-ready OpenShift 4.20.13 cluster on vSphere with three control plane nodes (ocpqa-master-0/1/2) running etcd quorum, three compute nodes (ocpqa-worker-0/1/2) for workloads, and vCenter Server Appliance managing ESXi hosts. Load Balancer VIPs distribute traffic to control and compute planes, while DNS/DHCP, Bastion Host, and Firewall provide infrastructure services ac