Merge pull request #68678 from DCChadwick/osdocs7897

OSDOCS-7897: Support cluster-wide proxy on Windows Containers

Author: jldohmann

modules/windows-containers-release-notes-limitations.adoc

@@ -25,8 +25,6 @@ Note the following limitations when working with Windows nodes managed by the WM
 
 * 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.
 
 * {productwinc} 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.

windows_containers/enabling-windows-container-workloads.adoc

@@ -40,11 +40,6 @@ Windows instances deployed by the WMCO are configured with the containerd contai
 
 You can install the Windows Machine Config Operator using either the web console or OpenShift CLI (`oc`).
 
-[NOTE]
-====
-The WMCO is not supported in clusters that use a xref:../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide proxy] because the WMCO is not able to route traffic through the proxy connection for the workloads.
-====
-
 include::modules/installing-wmco-using-web-console.adoc[leveloffset=+2]
 
 include::modules/installing-wmco-using-cli.adoc[leveloffset=+2]

windows_containers/scheduling-windows-workloads.adoc

@@ -8,11 +8,6 @@ toc::[]
 
 You can schedule Windows workloads to Windows compute nodes.
 
-[NOTE]
-====
-The WMCO is not supported in clusters that use a xref:../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide proxy] because the WMCO is not able to route traffic through the proxy connection for the workloads.
-====
-
 [discrete]
 == Prerequisites