Solution Pattern: Run your private workloads in Disconnected HCP OpenShift clusters with OpenShift Virtualization
Architecture
-
What is HCP:
Hosted Control Plane (HCP) is often referred to as "HyperShift" is an architectural innovation that allows for the separation of the control plane from the worker nodes in OpenShift clusters. This separation enables the control plane to be hosted independently on a managed infrastructure without the need for dedicated virtual or physical machines, which provides several benefits, especially in terms of scalability, resource efficiency, and management overhead.
-
What is Disconnected HCP:
Disconnected HCP is an OpenShift Container Platform deployment that is not connected to the internet and that uses Hosted Control Planes as a base. We can deploy hosted control planes in a disconnected environment on bare metal or OpenShift Virtualization. Hosted control planes in disconnected environments function differently than in standalone OpenShift Container Platform:
-
The control plane is in the management cluster. The control plane is where the pods of the hosted control plane are run and managed by the Control Plane Operator.
-
The data plane is in the workers of the hosted cluster. The data plane is where the workloads and other pods run, all managed by the HostedClusterConfig Operator.
1. An in-depth look at the solution’s architecture
This solution presents an architectural solution demonstrating how you can provision Disconnected Hosted Control Planes OpenShift clusters using OpenShift Virtualization. We will be first mirroring the required images to the internal registry and then using OpenShift Virtualization we will provision disconnected hosted control plane OpenShift cluster.