This is a cache of https://docs.okd.io/latest/windows_containers/wmco_rn/windows-containers-release-notes-10-17-x-limitations.html. It is a snapshot of the page at 2024-11-23T19:13:11.034+0000.
Windows Machin<strong>e</strong> Config Op<strong>e</strong>rator known limitations - R<strong>e</strong>l<strong>e</strong>as<strong>e</strong> not<strong>e</strong>s | Windows Contain<strong>e</strong>r Support for Op<strong>e</strong>nShift | OKD 4
  1. Documentation
&times;

Windows Machine Config Operator known limitations

Note the following limitations when working with Windows nodes managed by the WMCO (Windows nodes):

  • The following OKD features are not supported on Windows nodes:

    • Image builds

    • OpenShift Pipelines

    • OpenShift Service Mesh

    • OpenShift monitoring of user-defined projects

    • OpenShift Serverless

    • Horizontal Pod Autoscaling

    • Vertical Pod Autoscaling

  • The following Red Hat features are not supported on Windows nodes:

  • Dual NIC is not supported on WMCO-managed Windows instances.

  • Windows nodes do not support workloads created by using deployment configs. You can use a deployment or other method to deploy workloads.

  • Red Hat OpenShift support for Windows Containers does not support adding Windows nodes to a cluster through a trunk port. The only supported networking configuration for adding Windows nodes is through an access port that carries traffic for the VLAN.

  • Red Hat OpenShift support for Windows Containers does not support any Windows operating system language other than english (United States).

  • Due to a limitation within the Windows operating system, clusterNetwork CIDR addresses of class e, such as 240.0.0.0, are not compatible with Windows nodes.

  • Kubernetes has identified the following node feature limitations :

    • Huge pages are not supported for Windows containers.

    • Privileged containers are not supported for Windows containers.

    • Pod termination grace periods require the containerd container runtime to be installed on the Windows node.

  • Kubernetes has identified several API compatibility issues.