Merge pull request #44194 from openshift-cherrypick-robot/cherry-pick-42150-to-main

[main] WMCO 5.0.0 release notes

Author: mburke5678

_topic_maps/_topic_map.yml

@@ -1997,7 +1997,7 @@ Topics:
 - Name: Windows Container Support for Openshift overview
   File: index
 - Name: Windows Container Support for OpenShift release notes
-  File: windows-containers-release-notes-4-x
+  File: windows-containers-release-notes-5-x
 - Name: Understanding Windows container workloads
   File: understanding-windows-container-workloads
 - Name: Enabling Windows container workloads

windows_containers/index.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Windows Container Support for OpenShift is a feature providing the ability to run Windows compute nodes in an {product-title} cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With a Red Hat subscription, you can get support for running Windows workloads in {product-title}. For more information, see the xref:../windows_containers/windows-containers-release-notes-4-x.adoc#windows-containers-release-notes-4-x[release notes].
+Windows Container Support for OpenShift is a feature providing the ability to run Windows compute nodes in an {product-title} cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With a Red Hat subscription, you can get support for running Windows workloads in {product-title}. For more information, see the xref:../windows_containers/windows-containers-release-notes-5-x.adoc#windows-containers-release-notes-5-x[release notes].
 
 For workloads including both Linux and Windows, {product-title} allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on {op-system-first} or {op-system-base-full}. For more information, see xref:../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[getting started with Windows container workloads].
 

windows_containers/windows-containers-release-notes-4-x.adoc

@@ -0,0 +1,35 @@
+:_content-type: ASSEMBLY
+[id="windows-containers-release-notes-5-x"]
+= Windows Container Support for Red Hat OpenShift release notes
+include::_attributes/common-attributes.adoc[]
+:context: windows-containers-release-notes
+
+toc::[]
+
+[id="about-windows-containers"]
+== About Windows Container Support for Red Hat OpenShift
+
+Windows Container Support for Red Hat OpenShift enables running Windows compute nodes in an {product-title} cluster. Running Windows workloads 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 {product-title}.
+
+The release notes for Red Hat OpenShift for Windows Containers tracks the development of the WMCO, which provides all Windows container workload capabilities in {product-title}.
+
+[id="getting-support"]
+== 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 link:http://access.redhat.com/[Red Hat Customer Portal].
+
+[id="wmco-5-0-0"]
+== Release notes for Red Hat Windows Machine Config Operator 5.0.0
+
+This release of the WMCO provides bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 5.0.0 were released in link:https://access.redhat.com/errata/RHSA-2022:0577[RHSA-2022:0577].
+
+* Previously, Windows Containers on Windows Nodes could get assigned an incorrect DNS server IP. This caused DNS resolution to fail. This fix removes the hard-coded cluster DNS information and the DNS server IP is now passed as a command-line argument. As a result, Windows Containers on Windows Nodes get assigned a valid DNS Server IP and DNS resolution works for Windows workloads. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1994859[**BZ#1994859**])
+
+* Previously, certain commands being run by the WMCO against Windows VMs that used PowerShell as the default SSH shell were not parsed correctly. As a result, these VMs could not be added to a cluster as a node. With this fix the WMCO identifies the default SSH shell of a VM and runs commands accordingly. As a result, VMs with PowerShell as the default SSH shell can now be added to the cluster as a node. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2000772[**BZ#2000772**])
+
+* Previously, if a Bring-Your-Own-Host (BYOH) VM was specified with a DNS object, the WMCO was not properly associating the VM with its node object. This caused the WMCO to attempt to configure VMs that were already fully configured. With this fix the WMCO correctly resolves the DNS address of the VMs when looking for an associated node. As a result, BYOH VMs are now only configured when needed. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2005360[**BZ#2005360**])
+
+* Previously, if the `windows-exporter` metrics endpoint object contained a reference to a deleted machine, the WMCO ignored `Deleting` phase notification event for  those machines. This fix removes the validation of the machine object from event filtering. As a result, the `windows-exporter` metrics endpoint object is correctly updated even when the machine is still deleting. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2008601[**BZ#2008601**])
+
+* Previously, if an entity other than the WMCO modified the certificate signing request (CSR) associated with a BYOH node, the WMCO would have a stale reference to the CSR and would be unable to approve it. With this fix, if an update conflict is detected, the WMCO retries the CSR approval until a specified timeout. As a result, the CSR processing completes as expected. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2032048[**BZ#2032048**])
+