About Windows Container Support for Red Hat OpenShift

Windows Container Support for Red Hat OpenShift is a feature providing the ability to run Windows compute nodes in an OKD cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With Windows nodes available, you can run Windows container workloads in OKD.

The release notes for Red Hat OpenShift for Windows Containers tracks the development of the WMCO, which provides all Windows container workload capabilities in OKD.

Getting support

You must have a subscription to receive support for the Red Hat WMCO. Deploying Windows container workloads in production clusters is not supported without a subscription. If you do not have a subscription, you can use the community WMCO, a distribution that lacks official support. Request support through the Red Hat Customer Portal.

Release notes for Red Hat Windows Machine Config Operator 2.0.0

This release of the WMCO provides bug fixes and enhancements for running Windows compute nodes in an OKD cluster. The components of the WMCO 2.0.0 were released in RHBA-2021:0440.

WMCO supports self-managed clusters built using installer-provisioned infrastructure running on the following cloud providers:

  • Amazon Web Services (AWS)

  • Microsoft Azure

  • VMware vSphere

The following Windows Server operating systems are supported in this release of the WMCO, depending on which platform your cluster is installed on:

WMCO platform Windows Server version

AWS

Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019

Azure

Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019

vSphere

Windows Server Semi-Annual Channel (SAC): Windows Server 1909 with Microsoft patch KB4565351

Running Windows container workloads is not supported for clusters in a restricted network or disconnected environment.

Version 2.x of the WMCO is only compatible with OKD 4.7.

New features and improvements

This release adds the following new features and improvements.

Support for clusters running on VMware vSphere

You can now run Windows nodes on a cluster installed on VMware vSphere version 6.5, 6.7, or 7.0. You can create a Windows MachineSet object on vSphere to host Windows Server compute nodes. For more information, see Creating a Windows MachineSet object on vSphere.

Enhanced Windows node monitoring

Windows nodes are now fully integrated with most of the monitoring capabilities provided by the web console. However, it is not possible to view workload graphs for pods running on Windows nodes in this release.

Known issues

  • The filesystem graphs available in the web console do not display for Windows nodes. This is caused by changes in the filesystem queries. This will be fixed in a future release of WMCO. (BZ#1930347)

  • The Prometheus windows_exporter used by the WMCO currently collects metrics through HTTP, so it is considered unsafe. You must ensure that only trusted users can retrieve metrics from the endpoint. The windows_exporter feature recently added support for HTTPS configuration, but this configuration has not been implemented for WMCO. Support for HTTPS configuration in the WMCO will be added in a future release.

  • The kube-proxy service terminates unexpectedly after the load balancer is created if you create the load balancer after the Windows pods begin running. To avoid this issue, you must create the load balancer before the Windows pods status transitions to Running. (BZ#1939968)