Learn about OpenShift Virtualization architecture.
After you install OpenShift Virtualization, the Operator Lifecycle Manager (OLM) deploys operator pods for each component of OpenShift Virtualization:
OLM also deploys the
hyperconverged-cluster-operator pod, which is responsible for the deployment, configuration, and life cycle of other components, and several helper pods:
After all operator pods are successfully deployed, you should create the
HyperConverged custom resource (CR). The configurations set in the
HyperConverged CR serve as the single source of truth and the entrypoint for OpenShift Virtualization, and guide the behavior of the CRs.
HyperConverged CR creates corresponding CRs for the operators of all other components within its reconciliation loop. Each operator then creates resources such as daemon sets, config maps, and additional components for the OpenShift Virtualization control plane. For example, when the
hco-operator creates the
KubeVirt CR, the
virt-operator reconciles it and create additional resources such as
The OLM deploys the
hostpath-provisioner-operator, but it is not functional until you create a
hostpath provisioner (HPP) CR.