Openshift is a very flexible cloud platform supporting different deployment topologies, below are the most common flavors of openshift
Openshift separate control plane
The most commonly used deployment topology with separate three master nodes and any number of worker nodes
Openshift three node
You can deploy zero compute machines in a bare metal cluster that consists of three control plane machines only (collocated master and worker nodes). This provides smaller, more resource efficient clusters specially when low configuration physical servers are not an option.
https://lnkd.in/ekRsVCVF
Openshift remote worker nodes
A typical cluster with remote worker nodes combines on-premise masters and workers nodes with additional worker nodes in other remote locations.
Main cluster and remote worker nodes must run on the same infrastructure provider, a heartbeat is done every 10 seconds to make sure worker nodes are healthy.
https://lnkd.in/e6Xix95B
Single Node Openshift (SNO)
All in one setup where all openshift services run on a single node, Installing OpenShift on a single node requires a discovery ISO, which the Assisted Installer (AI) can generate with the cluster name, base domain, Secure Shell (SSH) public key, and pull secret.
https://lnkd.in/eNvYRk9g
Hypershift
Hosted control plane, where one openshift cluster can host the control planes of many other openshift clusters - Hosted Clusters - within namespaces. This model is very helpful for cost and time to provision, as well as portability cross cloud with strong separation of concerns between management and workloads.
https://lnkd.in/eZYpwF5a
Nested Openshift
Using openshift virtualization to provision the infrastructure - VMs - required to host another openshift cluster on top of it, So we end up having an openshift infrastructure cluster used to provision VMs to be used to host new openshift clusters (hosted clusters).
https://lnkd.in/eNuUYWS5
(found from Wael Eldoamiry)
Openshift is a very flexible cloud platform supporting different deployment topologies, below are the most common flavors of openshift
Openshift separate control plane The most commonly used deployment topology with separate three master nodes and any number of worker nodes
Openshift three node You can deploy zero compute machines in a bare metal cluster that consists of three control plane machines only (collocated master and worker nodes). This provides smaller, more resource efficient clusters specially when low configuration physical servers are not an option. https://lnkd.in/ekRsVCVF
Openshift remote worker nodes A typical cluster with remote worker nodes combines on-premise masters and workers nodes with additional worker nodes in other remote locations. Main cluster and remote worker nodes must run on the same infrastructure provider, a heartbeat is done every 10 seconds to make sure worker nodes are healthy. https://lnkd.in/e6Xix95B
Single Node Openshift (SNO) All in one setup where all openshift services run on a single node, Installing OpenShift on a single node requires a discovery ISO, which the Assisted Installer (AI) can generate with the cluster name, base domain, Secure Shell (SSH) public key, and pull secret. https://lnkd.in/eNvYRk9g
Hypershift Hosted control plane, where one openshift cluster can host the control planes of many other openshift clusters - Hosted Clusters - within namespaces. This model is very helpful for cost and time to provision, as well as portability cross cloud with strong separation of concerns between management and workloads. https://lnkd.in/eZYpwF5a
Nested Openshift Using openshift virtualization to provision the infrastructure - VMs - required to host another openshift cluster on top of it, So we end up having an openshift infrastructure cluster used to provision VMs to be used to host new openshift clusters (hosted clusters). https://lnkd.in/eNuUYWS5