This is a cache of https://docs.okd.io/latest/windows_containers/wmco_rn/windows-containers-release-notes-limitations.html. It is a snapshot of the page at 2026-07-07T19:20:22.317+0000.
Windows Machine Config Operator known limitations - Release notes | Windows Container Support for OpenShift | OKD 4
  1. Documentation
×

Windows Machine Config Operator known limitations

You should familiarize yourself with the set of known limitations when working with Windows nodes managed by the Windows Machine Config Operator (WMCO).

Note the following limitations when working with 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

    • Hosted Control Planes

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

    • Red Hat Lightspeed cost management

    • Red Hat OpenShift Local

  • 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. For more information, see "Compatibility and limitations (Kubernetes documenation)" in the Additional resources section.

    • 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. For more information, see "API compatibility (Kubernetes documenation)" in the Additional resources section.

Additional resources