Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 2. Prerequisites for virtualized control planes

Before deploying a virtualized control plane cluster, ensure your environment meets the following requirements.

Important

KubeVirt Redfish is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

2.1. Hosting cluster requirements
Link kopieren

The hosting cluster runs the virtualized control plane VMs and manages their lifecycle through KubeVirt Redfish.

The hosting cluster requires the following components:

  • OpenShift Container Platform installed and operational.
  • OpenShift Virtualization installed and configured.
  • Sufficient compute resources to host control plane VMs.
  • At least three physical nodes to enable anti-affinity placement, ensuring control plane VMs are spread across different physical hosts.

2.2. Storage requirements
Link kopieren

The hosting cluster must have a storage solution that supports VM disk images and meets the latency requirements of etcd.

The hosting cluster must have one of the following storage solutions:

  • Red Hat OpenShift Data Foundation (ODF) provides VM live migration. When you install ODF on a cluster where OpenShift Virtualization is running, the ocs-storagecluster-ceph-rbd-virtualization storage class is created automatically. This storage class is optimized for KubeVirt workloads.
  • Logical Volume Manager (LVM) Storage, backed by NVMe drives, provides predictable, low-latency disk I/O but does not support VM live migration.

Consider the following when choosing a storage solution:

  • ODF replicates data across multiple storage nodes for durability. This replication can cause unpredictable latency spikes during synchronization, which might affect etcd performance. Monitor etcd disk latency in production and ensure the underlying storage nodes use NVMe disks.
  • LVM Storage writes directly to local disks without replication, providing consistent low latency. However, data is not replicated across nodes.

2.3. Network requirements
Link kopieren

Virtualized control plane deployments require specific network connectivity between VMs, worker nodes, and external services.

Configure networking to meet the following requirements:

  • L2 network connectivity between control plane VMs. The OpenShift Container Platform installation program requires all control plane nodes to share the same L2 network segment.
  • L3 connectivity without network address translation (NAT) between the control plane VMs and worker nodes. Worker nodes must be able to route traffic directly to the control plane VMs. During installation, the bootstrap VM also requires L3 connectivity to the control plane.
  • External access to the cluster API.
  • Access to container image registries.
  • DNS resolution for cluster components.

You can use either dynamic or static IP addressing for the control plane VMs:

  • For deployments that use DHCP, configure static MAC addresses on the primary network interfaces of the VMs and create DHCP reservations for each MAC address. This ensures consistent IP assignment across VM restarts.
  • For deployments that use static IP addressing, define the network configuration in your install-config.yaml or Agent-based installation manifests.

2.4. Control plane VM requirements
Link kopieren

Each control plane VM must meet minimum resource requirements to run the OpenShift Container Platform control plane components reliably.

Each control plane VM requires the following minimum resources:

  • 8 vCPUs
  • 16 GiB RAM
  • 120 GiB storage

2.5. KubeVirt Redfish requirements
Link kopieren

KubeVirt Redfish exposes VMs through the Redfish API.

You need the following to use KubeVirt Redfish:

  • Network access from the installation workstation to the KubeVirt Redfish route.
  • Credentials configured in KubeVirt Redfish for API authentication.
  • VMs labeled to be exposed through the Redfish API.
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Legal Notice

Theme

© 2026 Red HatNach oben