You can deploy Bare Metal Orchestrator on Linux Ubuntu 20.04 or Red Hat Enterprise Linux 8.6 environments running on bare metal or hypervisors as a five-node high availability (HA) cluster.
On-premises HA cluster installation
Bare Metal Orchestrator installs an RKE2 (next-generation) cluster called the Global Controller (GC) node, which is also called control plane 1 (CP1).
The RKE2 cluster includes the Global Controller (CP1), two redundant high availability nodes (CP2 and CP3), and a redundant pair of Load Balancers.
The same operating system (either Ubuntu 20.04 LTS or Red Hat Enterprise Linux 8.6) must be used on all nodes in the cluster, including the Global Controller (CP1), the two redundant HA nodes (CP2 and CP3), and the Load Balancers.
For a workflow of the installation process, see Installation workflow.
For information about high availability node deployment requirements, see:
HA installation on AWS with an AWS EC2 network load balancer
You can use an AWS EC2 network load balancer instead of the two default redundant load balancers supplied in the Bare Metal Orchestrator RKE2 cluster. The installation on AWS EC2 consists of three EC2 nodes that form the control plane. The following figure shows the HA installation on AWS with an AWS EC2 network load balancer.
The deployment process on AWS EC2 is similar to the on-premises HA cluster installation process. However, the AWS load balancing service is used instead of the default load balancers in the Bare Metal Orchestrator cluster. You must ensure that all ports are open for the AWS EC2 network load balancer to work with Bare Metal Orchestrator.
For more information about the port requirements, see Network requirements.
For more information, see Configure an HA Bare Metal Orchestrator cluster on AWS EC2.