Red HatSerena FloccoTutorial
Hosted control planes for Red Hat OpenShift, based on the HyperShift project, decouple the cluster control plane from worker nodes by running control-plane components as pods inside a central management cluster. On bare-metal infrastructure, OpenShift Virtualization provisions worker nodes as virtual machines, enabling live migration and reducing hardware requirements. The article presents a declarative GitOps workflow using Helm templates and an Argo CD ApplicationSet that dynamically generates deployments from tenant-specific YAML configuration files in Git. Prerequisites include a bare-metal management cluster with OpenShift Virtualization, Red Hat Advanced Cluster Management, and OpenShift GitOps, plus networking configured with NMState, Multus CNI, and MetalLB. The approach achieves a “Cluster-as-a-Service” model where provisioning a production-grade cluster requires only a Git push.
Enterprise data centers running bare-metal infrastructure face hardware underutilization when each new Red Hat OpenShift cluster requires at least three physical nodes for its control plane. Traditional provisioning multiplies this footprint across environments. Hosted control planes, based on the HyperShift project, decouple the control plane from worker nodes by running control-plane components as pods inside a central management cluster, reducing infrastructure costs and enabling fast cluster provisioning. This article presents a declarative, production-ready GitOps workflow that combines hosted control planes with Red Hat OpenShift Virtualization to run worker nodes as virtual machines, scaling cluster deployment on bare metal.
The solution involves a three-layer GitOps workflow using Helm templates and an Argo CD ApplicationSet on a bare-metal management cluster. Worker node configurations are stored as simple YAML files in a clusters/ directory, while immutable infrastructure code resides in a helm/ directory. When a new configuration file is pushed to Git, the ApplicationSet dynamically generates the Helm deployment, which creates the hosted control plane pods, worker node VMs, and registers the new cluster with Red Hat Advanced Cluster Management. The management cluster runs OpenShift Virtualization, Red Hat Advanced Cluster Management with its MultiClusterEngine Operator, and OpenShift GitOps.
Hosted control planes run control-plane components as pods in a central management cluster, eliminating the need for three dedicated physical nodes per cluster on bare-metal infrastructure.
Worker nodes are provisioned as virtual machines via OpenShift Virtualization, which requires a ReadWriteMany (RWX) storage backend like Red Hat OpenShift Data Foundation to support live migration between physical hosts.
An Argo CD ApplicationSet combined with Helm allows automated cluster provisioning from Git: a tenant-specific YAML file in the clusters/ directory triggers dynamic deployment generation without manual intervention.
Summaries are generated from the original by a language model. Check the original before relying on it.
See the idea
Bare metal gives engineers direct control over GPU, network, and virtualization layers, but it shifts elasticity and lifecycle work onto the team. This trade-off map shows when that bargain pays off.
Keep reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
One useful email. Unsubscribe anytime.
