Merge pull request #28230 from codyhoag/windows-server-version-update

Version recommendation update for WINC

Author: codyhoag

modules/windows-machineset-aws.adoc

@@ -80,7 +80,7 @@ $ oc get -o jsonpath='{.status.infrastructureName}{"\n"}' infrastructure cluster
 <2> Specify the infrastructure ID, worker label, and zone.
 <3> Configure the machine set as a Windows machine.
 <4> Configure the Windows node as a compute machine.
-<5> Specify the AMI ID of a Windows image with a container runtime installed. You must use Windows Server 2019 with a version 10.0.17763.1457 or later.
+<5> Specify the AMI ID of a Windows image with a container runtime installed. You must use Windows Server 2019 with a version 10.0.17763.1457 or earlier.
 <6> Specify the AWS zone, like `us-east-1a`.
 <7> Specify the AWS region, like `us-east-1`.
 <8> Created by the WMCO when it is configuring the first Windows machine. After that, the `windows-user-data` is available for all subsequent machine sets to consume.

modules/windows-machineset-azure.adoc

@@ -74,7 +74,7 @@ $ oc get -o jsonpath='{.status.infrastructureName}{"\n"}' infrastructure cluster
 <2> Specify the infrastructure ID, worker label, and region.
 <3> Configure the machine set as a Windows machine.
 <4> Configure the Windows node as a compute machine.
-<5> Specify a `WindowsServer` image offering that defines the `2019-Datacenter-with-Containers` SKU with version `17763.1457.2009030514` or later.
+<5> Specify a `WindowsServer` image offering that defines the `2019-Datacenter-with-Containers` SKU with version `17763.1457.2009030514` or earlier.
 <6> Specify the Azure region, like `centralus`.
 <7> Created by the WMCO when it is configuring the first Windows machine. After that, the `windows-user-data` is available for all subsequent machine sets to consume.
 <8> Specify the zone within your region to place machines on. Be sure that your region supports the zone that you specify.

windows_containers/windows-containers-release-notes.adoc

@@ -34,7 +34,7 @@ The following Windows Server operating systems are supported in the initial rele
 [id="wmco-1-0-1-known-issues"]
 === Known issues
 
-* If you have a cluster with two Windows nodes, and you create a web server deployment with two replicas, the pods each land on a Windows compute node. In this scenario, if you create a `Service` object with type `LoadBalancer`, communication with the load balancer endpoint is flaky. To mitigate this issue, you must use Windows Server 2019 with a version 10.0.17763.1457 or later. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1905950[*BZ#1905950*])
+* If you have a cluster with two Windows nodes, and you create a web server deployment with two replicas, the pods each land on a Windows compute node. In this scenario, if you create a `Service` object with type `LoadBalancer`, communication with the load balancer endpoint is flaky. To mitigate this issue, you must use Windows Server 2019 with a version 10.0.17763.1457 or earlier. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1905950[*BZ#1905950*])
 +
 To pick the correct image for the `MachineSet` object, follow the instructions based on your cloud provider:
 +
@@ -72,7 +72,7 @@ $ az vm image list --all --location <location> \// <1>
 ----
 <1> Specify the location your cluster is using.
 
-. Find a `WindowsServer` image offering that defines the `2019-Datacenter-with-Containers` SKU with version `17763.1457.2009030514` or later.
+. Find a `WindowsServer` image offering that defines the `2019-Datacenter-with-Containers` SKU with version `17763.1457.2009030514` or earlier.
 +
 .Example output
 ----