Past releases - Release notes | Windows Container Support for OpenShift

You can review the following release notes to learn about changes in previous versions of the Custom Metrics Autoscaler Operator.

Release notes for Red Hat Windows Machine Config Operator 10.17.1

Issued: 9 June 2025

You can review the following release notes to learn about the bug fixes provided in this release of the Windows Machine Config Operator (WMCO).

The components of the WMCO 10.17.1 were released in RHSA-2025:8704.

WMCO now defaults to info-level logging: The WMCO is configured to use the info log level by default. You can change the log level to debug by editing the WMCO subscription object.

For more information, see Configuring debug-level logging for the Windows Machine Config Operator.

Before this update, Windows nodes were unable to pull from image mirror registries if an organization name or namespace was included in the source of the ImageTagMirrorSet (ITMS) object. With this fix, you can include an organization name or namespace in the ITMS object. With this release, additional guidelines and requirements around using mirror registries have been added to the OKD documentation. For more information, see Using Windows containers with a mirror registry. (OCPBUGS-55915)
Before this update, the OKD documentation lacked information about WMCO support for the installer-provisioned infrastructure and the user-provisioned infrastructure installation methods. With this release, the documentation reports that the installer-provisioned infrastructure method is the preferred installation method and can be used with all platforms. The user-provisioned infrastructure method is limited to specific use cases. For more information, see WMCO supported installation method. (OCPBUGS-44237)

You can review the following release notes to learn about the bug fixes provided in this release of the Windows Machine Config Operator (WMCO).

The components of the WMCO 10.17.0 were released in RHSA-2024:7436.

Before this update, if a Windows VM had its PowerShell ExecutionPolicy set to Restricted, the Windows Instance Config Daemon (WICD) could not run the commands on that VM that are necessary for creating Windows nodes. With this release, the WICD now bypasses the execution policy on the VM when running PowerShell commands. As a result, the WICD can create Windows nodes on the VM as expected. (OCPBUGS-30995)

Before this update, if reverse DNS lookup failed due to an error, such as the reverse DNS lookup services being unavailable, the WMCO would not fall back to using the VM hostname to determine if a certificate signing requests (CSR) should be approved. As a consequence, Bring-Your-Own-Host (BYOH) Windows nodes configured with an IP address would not become available. With this release, BYOH nodes are properly added if reverse DNS is not available. (OCPBUGS-36643)

Before this update, if there were multiple service account token secrets in the WMCO namespace, scaling Windows nodes would fail. With this release, the WMCO uses only the secret it creates, ignoring any other service account token secrets in the WMCO namespace. As a result, Windows nodes scale properly. (OCPBUGS-29253)