10.4. Heterogeneous cluster support


A heterogeneous cluster is a cluster where nodes have differing architectures. Heterogeneous clusters promote optimal compute resource usage by mixing different types of hardware in one cluster.

With heterogeneous clusters, you can match workloads to hardware intended for the workload task instead of general purpose compute platforms. For example, you can combine GPU and general purpose compute resources and assign workloads to the appropriate hardware.

If you have a heterogeneous cluster but do not want to enable multiple architecture support, you can modify the workloads node placement in the HyperConverged custom resource (CR) to include only nodes with a specific architecture.

With boot source image support, you can deploy persistent VMs with specific architectures and define custom boot images that support heterogeneous clusters.

중요

If you do not enable boot source image support in a heterogeneous cluster, images might not match the node architecture. As a result, virtual machines might fail to start or might not run as expected. OpenShift Virtualization raises the HCOMultiArchGoldenImagesDisabled alert when this feature is not enabled.

The same image can be used with nodes of different architectures if the boot image supports the required architectures. For example, a boot image that supports both ARM and AMD architectures can be used with both types of nodes.

Boot source image support for heterogeneous clusters is not enabled by default. You can enable heterogeneous cluster support by setting the feature gate in the HyperConverged CR.

10.4.1. Default architecture behavior in heterogeneous clusters

In a heterogeneous cluster, worker nodes run different CPU architectures, such as amd64 and arm64. A boot source image built for one architecture cannot start on a node with a different architecture.

To prevent architecture mismatches, OpenShift Virtualization creates a separate boot source for each supported architecture, each represented by a DataSource object.

중요

If you have a heterogeneous cluster and do not enable the enableMultiArchBootImageImport field, VMs might fail to start on nodes with a different architecture than the boot source image.

10.4.1.1. How data sources for boot source images work in heterogeneous clusters

After you enable the enableMultiArchBootImageImport field, the Scheduling, Scale, and Performance (SSP) Operator creates a new separate boot source for each supported architecture, represented by a DataSource object. For example, the rhel9 boot source image gets the following data sources:

  • rhel9-amd64
  • rhel9-arm64

The original name, such as rhel9, defaults to the boot source that matches the control-plane architecture. For example, if the control-plane nodes use amd64, then rhel9 resolves to rhel9-amd64.

Existing VM manifests and templates that use the original name, without an architecture suffix, continue to work without changes.

For common boot sources that are provided by OpenShift Virtualization, the SSP Operator determines the supported architectures automatically. For custom boot sources that you add through the HyperConverged CR, you must specify the supported architectures by using the ssp.kubevirt.io/dict.architectures annotation.

10.4.1.2. Default architecture for standalone VMs

A VM that is not based on a boot source image, for example a VM from a container disk, HTTP source, upload, or clone, defaults to the control-plane architecture. The spec.template.spec.architecture field in the VirtualMachine manifest controls which architecture the VM uses.

10.4.1.3. Default architecture for standalone data volumes

A DataVolume created directly from a registry source does not have a default architecture. Without an explicit architecture, CDI pulls whichever image variant the registry returns. The spec.source.registry.platform.architecture field in the DataVolume manifest controls which architecture to pull.

Red Hat logoGithubRedditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동