-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
4.18
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
[HyperShift][KubeVirt] Support Mixed NodePools (Local + External InfraCluster) in Single HostedCluster
2. What is the nature and description of the request?
Requesting support for attaching both local and external NodePools to a single HostedCluster in a HyperShift-managed OpenShift environment using KubeVirt as the platform.
Current Behavior:
- HyperShift restricts a HostedCluster to NodePools that reference a single InfraCluster.
- Attempting to mix local NodePools (management cluster) and external NodePools (remote OpenShift clusters via KubeVirt) is unsupported and results in failure or undefined behavior.
Expected Behavior:
- A HostedCluster should be able to:
-
- Reference multiple InfraClusters (e.g., local and one or more remote OpenShift Virtualization clusters).
-
- Schedule NodePools across these clusters transparently.
-
- Retain full lifecycle automation, upgrade capabilities, and workload compatibility.
This enhancement enables:
- Hybrid node placement: Start with local resources and burst into remote infrastructure.
- Edge computing use cases: Deploy workloads close to data sources while retaining centralized control.
- Disaster recovery: Seamless recovery or load redistribution across sites.
- Resource efficiency: Avoid overprovisioning local infra when remote capacity is available.
3. Why does the customer need this? (List the business requirements here)
- Inability to deploy unified HostedCluster across available infrastructure boundaries.
- Increases overhead with multiple HostedClusters and complex app orchestration.
- Blocks adoption for hybrid, multi-site, and DR scenarios using HyperShift.
4. List any affected packages or components.
Hypershift, OCPV