Updated the WMCO documentation to include a prerequisite module

modules/wmco-prerequisites.adoc

@@ -0,0 +1,87 @@
+// Module included in the following assemblies:
+//
+// * windows_containers/understanding-windows-container-workloads.adoc
+
+[id="wmco-prerequisites_{context}"]
+= Windows Machine Config Operator prerequisites
+
+The following information details the supported cloud provider versions, Windows Server versions, and networking configurations for the Windows Machine Config Operator. See the vSphere documentation for any information that is relevant to only that platform.
+
+== Supported cloud providers based on {product-title} and WMCO versions
+
+[cols="3",options="header"]
+|===
+|Cloud provider
+|Supported {product-title} version
+|Supported WMCO version
+
+|Amazon Web Services (AWS)
+|4.6+
+|WMCO 1.0+
+
+|Microsoft Azure
+|4.6+
+|WMCO 1.0+
+
+|VMware vSphere
+|4.7+
+|WMCO 2.0+
+|===
+
+== Supported Windows Server versions
+
+The following table lists the supported link:https://docs.microsoft.com/en-us/windows/release-health/release-information[Windows Server version] based on the applicable cloud provider. Any unlisted Windows Server version is not supported and will cause errors. To prevent these errors, only use the appropriate version according to the cloud provider in use.
+
+[cols="2",options="header"]
+|===
+|Cloud provider
+|Supported Windows Server version
+
+|Amazon Web Services (AWS)
+|Windows Server Long-Term Servicing Channel (LTSC): Windows Server 1809
+
+|Microsoft Azure
+|Windows Server Long-Term Servicing Channel (LTSC): Windows Server 1809
+
+|VMware vSphere
+|Windows Server Semi-Annual Channel (SAC): Windows Server 2004
+|===
+
+== Supported networking
+
+Hybrid networking with OVN-Kubernetes is the only supported networking configuration. See the additional resources below for more information on this functionality. The following tables outline the type of networking configuration and Windows Server versions to use based on your cloud provider. You must specify the network configuration when you install the cluster. Be aware that OpenShift SDN networking is the default network for {product-title} clusters. However, OpenShift SDN is not supported by WMCO.
+
+
+.Cloud provider networking support
+[cols="2",options="header"]
+|===
+|Cloud provider
+|Supported networking
+
+|Amazon Web Services (AWS)
+|Hybrid networking with OVN-Kubernetes
+
+|Microsoft Azure
+|Hybrid networking with OVN-Kubernetes
+
+|VMware vSphere
+|Hybrid networking with OVN-Kubernetes with a custom VXLAN port
+|===
+
+.Hybrid OVN-Kubernetes Windows Server support
+[cols="2",options="header"]
+|===
+|Hybrid networking with OVN-Kubernetes
+|Supported Windows Server version
+
+|Default VXLAN port
+|Windows Server Long-Term Servicing Channel (LTSC): Windows Server 1809
+
+|Custom VXLAN port
+|Windows Server Semi-Annual Channel (SAC): Windows Server 2004
+|===
+
+== Supported installation method
+
+The installer-provisioned infrastructure installation method is the only supported installation method. This is
+consistent across all supported cloud providers. User-provisioned infrastructure installation method is not supported.

windows_containers/understanding-windows-container-workloads.adoc

@@ -26,6 +26,11 @@ Multi-tenancy for clusters that have Windows nodes is not supported. Hostile mul
 Windows Server Containers provide resource isolation using a shared kernel but are not intended to be used in hostile multitenancy scenarios. Scenarios that involve hostile multitenancy should use Hyper-V Isolated Containers to strongly isolate tenants.
 ====
 
+include::modules/wmco-prerequisites.adoc[leveloffset=+1]
+
+.Additional resources
+* See xref:../networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc#configuring-hybrid-ovnkubernetes_configuring-hybrid-networking[Configuring hybrid networking with OVN-Kubernetes]
+
 include::modules/windows-workload-management.adoc[leveloffset=+1]
 
 include::modules/windows-node-services.adoc[leveloffset=+1]