This is a cache of https://docs.openshift.com/container-platform/4.12/windows_containers/wmco_rn/windows-containers-release-notes-7-x-known-limitations.html. It is a snapshot of the page at 2024-11-22T12:20:42.621+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 | Op<strong>e</strong>nShift Contain<strong>e</strong>r Platform 4.12
&times;

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

  • The following OpenShift Container Platform 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.

  • Windows nodes are not supported in clusters that use a cluster-wide proxy. This is because the WMCO is not able to route traffic through the proxy connection for the workloads.

  • Windows nodes are not supported in clusters that are in a disconnected environment.

  • 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 supports only in-tree storage drivers for all cloud providers.

  • 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.

  • Kubernetes has identified several API compatibility issues.