1. Proposed title of this feature request

Add Support for BYOH Windows Nodes in Hosted Control Planes NodePools

Summary of Request:

Requesting support to add Windows BYOH (Bring Your Own Host) nodes as worker nodes in NodePools for Hosted Control Planes (HyperShift) clusters.

This support should ideally enable onboarding Windows nodes through:

• Agent-based (Assisted Service) workflows

• Windows VMs provisioned via OpenShift Virtualization (KubeVirt)

The goal is to enable consistent Windows workload support in HostedClusters, including disconnected, virtualized, and edge use cases.

---

2. Current Limitation:

Hosted Control Planes (HyperShift) currently support worker NodePools backed by:

• Public cloud infrastructure (AWS, etc.)

• Agent-based and KubeVirt-based Linux workers

• BYOH Linux nodes in specific advanced flows

However, there is no support for:

• Adding Windows nodes to HostedClusters

• Registering Windows hosts via Agent-based install

• Using OpenShift Virtualization to back Windows NodePools

This prevents users from running Windows containers in HostedControlPlane-managed clusters, especially when BYOH or virtualization is the only viable platform.

---

3. Business Justification / Customer Need:

• Customers running legacy or Windows-specific workloads require Windows worker node support across all OpenShift deployment models, including Hosted Control Planes.

• In air-gapped, disconnected, or on-premises environments, public cloud MachinePools are not viable, and virtualization or BYOH flows are preferred.

• Edge and telco customers often operate mixed workloads on constrained infrastructure and expect parity between classic and hosted cluster models.

• Organizations using OpenShift Virtualization to host Windows VMs want to use them as scalable NodePools in HostedClusters.

---

4. Proposed Enhancement:

Add native support for Windows worker NodePools in Hosted Control Planes, via:

a) Agent-based onboarding (Assisted Installer):

• Allow Windows hosts to be onboarded into NodePools using the existing InfraEnv and Agent resources.

• Support configuration/preparation workflows for pre-installed Windows kubelets and WMCO compatibility.

b) Windows VMs in OpenShift Virtualization:

• Enable HostedClusters to define NodePools running on Windows VMs created via KubeVirt/OpenShift Virtualization.

• Leverage Windows Machine Config Operator (WMCO) for node configuration and cluster join.

c) HyperShift API and NodePool extensions:

• Introduce osType: Windows in NodePool API.

• Support mixed-OS node pools (Windows + Linux) for hybrid workload deployment.

---

5. Benefits:

• Enables unified cluster management across Linux and Windows workloads in Hosted Control Planes.

• Supports edge, telco, and enterprise use cases that depend on Windows.

• Unlocks BYOH and KubeVirt integration for Windows, improving flexibility and deployment options.

---

6. Affected Components:

• Hosted Control Planes (HyperShift)

• NodePool controller

• Windows Machine Config Operator (WMCO)

• Assisted Installer (AgentServiceConfig/InfraEnv)

• OpenShift Virtualization (KubeVirt)

3. Why does the customer need this? (List the business requirements here)

Customer need this to make use of existing windows node for hypershift cluster.
4. List any affected packages or components.

hypershift, assisted-service, openshift-virtualization