Merge pull request #95507 from mburke5678/wmco-unhide-4.19

Revert 'WMCO hiding 4.19.0 docs'

Author: mburke5678

_topic_maps/_topic_map.yml

@@ -869,8 +869,8 @@ Topics:
     File: troubleshooting-s2i
   - Name: Troubleshooting storage issues
     File: troubleshooting-storage-issues
-#  - Name: Troubleshooting Windows container workload issues
-#    File: troubleshooting-windows-container-workload-issues
+  - Name: Troubleshooting Windows container workload issues
+    File: troubleshooting-windows-container-workload-issues
   - Name: Investigating monitoring issues
     File: investigating-monitoring-issues
   - Name: Diagnosing OpenShift CLI (oc) issues
@@ -2850,47 +2850,47 @@ Distros: openshift-origin,openshift-enterprise
 Topics:
 - Name: Red Hat OpenShift support for Windows Containers overview
   File: index
-#- Name: Release notes
-#  Dir: wmco_rn
-#  Topics:
-#  - Name: Red Hat OpenShift support for Windows Containers release notes
-#    File: windows-containers-release-notes-10-17-x
-#  - Name: Past releases
-#    File: windows-containers-release-notes-10-17-x-past
-#  - Name: Windows Machine Config Operator prerequisites
-#    File: windows-containers-release-notes-10-17-x-prereqs
-#  - Name: Windows Machine Config Operator known limitations
-#    File: windows-containers-release-notes-10-17-x-limitations
-#- Name: Getting support
-#  File: windows-containers-support
-#  Distros: openshift-enterprise
-#- Name: Understanding Windows container workloads
-#  File: understanding-windows-container-workloads
-#- Name: Enabling Windows container workloads
-#  File: enabling-windows-container-workloads
-#- Name: Creating Windows machine sets
-#  Dir: creating_windows_machinesets
-#  Topics:
-#  - Name: Creating a Windows machine set on AWS
-#    File: creating-windows-machineset-aws
-#  - Name: Creating a Windows machine set on Azure
-#    File: creating-windows-machineset-azure
-#  - Name: Creating a Windows machine set on GCP
-#    File: creating-windows-machineset-gcp
-#  - Name: Creating a Windows machine set on Nutanix
-#    File: creating-windows-machineset-nutanix
-#  - Name: Creating a Windows machine set on vSphere
-#    File: creating-windows-machineset-vsphere
-#- Name: Scheduling Windows container workloads
-#  File: scheduling-windows-workloads
-#- Name: Windows node updates
-#  File: windows-node-upgrades
-#- Name: Using Bring-Your-Own-Host Windows instances as nodes
-#  File: byoh-windows-instance
-#- Name: Removing Windows nodes
-#  File: removing-windows-nodes
-#- Name: Disabling Windows container workloads
-#  File: disabling-windows-container-workloads
+- Name: Release notes
+  Dir: wmco_rn
+  Topics:
+  - Name: Red Hat OpenShift support for Windows Containers release notes
+    File: windows-containers-release-notes-10-17-x
+  - Name: Past releases
+    File: windows-containers-release-notes-10-17-x-past
+  - Name: Windows Machine Config Operator prerequisites
+    File: windows-containers-release-notes-10-17-x-prereqs
+  - Name: Windows Machine Config Operator known limitations
+    File: windows-containers-release-notes-10-17-x-limitations
+- Name: Getting support
+  File: windows-containers-support
+  Distros: openshift-enterprise
+- Name: Understanding Windows container workloads
+  File: understanding-windows-container-workloads
+- Name: Enabling Windows container workloads
+  File: enabling-windows-container-workloads
+- Name: Creating Windows machine sets
+  Dir: creating_windows_machinesets
+  Topics:
+  - Name: Creating a Windows machine set on AWS
+    File: creating-windows-machineset-aws
+  - Name: Creating a Windows machine set on Azure
+    File: creating-windows-machineset-azure
+  - Name: Creating a Windows machine set on GCP
+    File: creating-windows-machineset-gcp
+  - Name: Creating a Windows machine set on Nutanix
+    File: creating-windows-machineset-nutanix
+  - Name: Creating a Windows machine set on vSphere
+    File: creating-windows-machineset-vsphere
+- Name: Scheduling Windows container workloads
+  File: scheduling-windows-workloads
+- Name: Windows node updates
+  File: windows-node-upgrades
+- Name: Using Bring-Your-Own-Host Windows instances as nodes
+  File: byoh-windows-instance
+- Name: Removing Windows nodes
+  File: removing-windows-nodes
+- Name: Disabling Windows container workloads
+  File: disabling-windows-container-workloads
 ---
 Name: OpenShift sandboxed containers
 Dir: sandboxed_containers

installing/installing_aws/ipi/installing-aws-network-customizations.adoc

@@ -109,13 +109,10 @@ include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+1]
 
 include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
 
-////
-Hiding until WMCO 10.19.0 GAs
 [NOTE]
 ====
-For more information about using Linux and Windows nodes in the same cluster, see ../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
+For more information about using Linux and Windows nodes in the same cluster, see xref:../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
 ====
-////
 
 include::modules/installation-launching-installer.adoc[leveloffset=+1]
 

installing/installing_azure/ipi/installing-azure-network-customizations.adoc

@@ -46,13 +46,10 @@ include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
 include::modules/nw-operator-cr.adoc[leveloffset=+1]
 include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
 
-////
-Hiding until WMCO 10.19.0 GAs
 [NOTE]
 ====
-For more information about using Linux and Windows nodes in the same cluster, see ../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
+For more information about using Linux and Windows nodes in the same cluster, see xref:../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
 ====
-////
 
 [role="_additional-resources"]
 .Additional resources

installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc

@@ -50,13 +50,10 @@ include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
 include::modules/nw-operator-cr.adoc[leveloffset=+1]
 include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
 
-////
-Hiding until WMCO 10.19.0 GAs
 [NOTE]
 ====
-For more information about using Linux and Windows nodes in the same cluster, see ../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
+For more information about using Linux and Windows nodes in the same cluster, see xref:../../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads].
 ====
-////
 
 include::modules/installation-launching-installer.adoc[leveloffset=+1]
 

installing/overview/installing-preparing.adoc

@@ -117,10 +117,7 @@ For a production cluster, you must configure the following integrations:
 
 Depending on your workload needs, you might need to take extra steps before you begin deploying applications. For example, after you prepare infrastructure to support your application xref:../../cicd/builds/build-strategies.adoc#build-strategies[build strategy], you might need to make provisions for xref:../../scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#cnf-low-latency-perf-profile[low-latency] workloads or to xref:../../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets[protect sensitive workloads]. You can also configure xref:../../observability/monitoring/configuring-user-workload-monitoring/preparing-to-configure-the-monitoring-stack-uwm.adoc#enabling-monitoring-for-user-defined-projects-uwm_preparing-to-configure-the-monitoring-stack-uwm[monitoring] for application workloads.
 
-////
-Hiding until WMCO 10.19.0 GAs
-If you plan to run ../../windows_containers/enabling-windows-container-workloads.adoc#enabling-windows-container-workloads[Windows workloads], you must enable xref:../../networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc#configuring-hybrid-networking[hybrid networking with OVN-Kubernetes] during the installation process; hybrid networking cannot be enabled after your cluster is installed.
-////
+If you plan to run xref:../../windows_containers/enabling-windows-container-workloads.adoc#enabling-windows-container-workloads[Windows workloads], you must enable xref:../../networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc#configuring-hybrid-networking[hybrid networking with OVN-Kubernetes] during the installation process; hybrid networking cannot be enabled after your cluster is installed.
 
 [id="supported-installation-methods-for-different-platforms"]
 == Supported installation methods for different platforms

modules/configuring-hybrid-ovnkubernetes.adoc

@@ -15,19 +15,14 @@ endif::[]
 
 You can configure your cluster to use hybrid networking with the OVN-Kubernetes network plugin. This allows a hybrid cluster that supports different node networking configurations.
 
-////
-Hiding until WMCO 10.19.0 GAs.  Swap the two sections after WMCO GA.
 [NOTE]
 ====
 This configuration is necessary to run both Linux and Windows nodes in the same cluster.
 ====
-////
 
 ifndef::post-install[]
 .Prerequisites
 
-// Made changes to hide Windows-related material until WMCO 4.19.0 releases. The full procedure is below, commented out.
-
 * You defined `OVNKubernetes` for the `networking.networkType` parameter in the `install-config.yaml` file. See the installation documentation for configuring {product-title} network customizations on your chosen cloud provider for more information.
 
 .Procedure
@@ -82,8 +77,15 @@ spec:
         hybridClusterNetwork: <1>
         - cidr: 10.132.0.0/14
           hostPrefix: 23
+        hybridOverlayVXLANPort: 9898 <2>
 ----
 <1> Specify the CIDR configuration used for nodes on the additional overlay network. The `hybridClusterNetwork` CIDR must not overlap with the `clusterNetwork` CIDR.
+<2> Specify a custom VXLAN port for the additional overlay network. This is required for running Windows nodes in a cluster installed on vSphere, and must not be configured for any other cloud provider. The custom port can be any open port excluding the default `4789` port. For more information on this requirement, see link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/common-problems#pod-to-pod-connectivity-between-hosts-is-broken-on-my-kubernetes-cluster-running-on-vsphere[Pod-to-pod connectivity between hosts is broken] in the Microsoft documentation.
++
+[NOTE]
+====
+Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019 is not supported on clusters with a custom `hybridOverlayVXLANPort` value because this Windows server version does not support selecting a custom VXLAN port.
+====
 --
 
 . Save the `cluster-network-03-config.yml` file and quit the text editor.
@@ -116,7 +118,8 @@ $ oc patch networks.operator.openshift.io cluster --type=merge \
                 "cidr": "<cidr>",
                 "hostPrefix": <prefix>
               }
-            ]
+            ],
+            "hybridOverlayVXLANPort": <overlay_port>
           }
         }
       }
@@ -129,6 +132,12 @@ where:
 
 `cidr`:: Specify the CIDR configuration used for nodes on the additional overlay network. This CIDR must not overlap with the cluster network CIDR.
 `hostPrefix`:: Specifies the subnet prefix length to assign to each individual node. For example, if `hostPrefix` is set to `23`, then each node is assigned a `/23` subnet out of the given `cidr`, which allows for 510 (2^(32 - 23) - 2) pod IP addresses. If you are required to provide access to nodes from an external network, configure load balancers and routers to manage the traffic.
+`hybridOverlayVXLANPort`:: Specify a custom VXLAN port for the additional overlay network. This is required for running Windows nodes in a cluster installed on vSphere, and must not be configured for any other cloud provider. The custom port can be any open port excluding the default `4789` port. For more information on this requirement, see link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/common-problems#pod-to-pod-connectivity-between-hosts-is-broken-on-my-kubernetes-cluster-running-on-vsphere[Pod-to-pod connectivity between hosts is broken] in the Microsoft documentation.
+
+[NOTE]
+====
+Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019 is not supported on clusters with a custom `hybridOverlayVXLANPort` value because this Windows server version does not support selecting a custom VXLAN port.
+====
 --
 +
 .Example output
@@ -143,11 +152,9 @@ network.operator.openshift.io/cluster patched
 ----
 $ oc get network.operator.openshift.io -o jsonpath="{.items[0].spec.defaultNetwork.ovnKubernetesConfig}"
 ----
-
 endif::post-install[]
-
-////
-Hiding until WMCO 10.19.0 GAs. Swap the two sections after WMCO GA.
+//// 
+Made changes to hide Windows-related material. Use this material instead of the above if the WMCO is not available at the time of an OCP release. 
 ifndef::post-install[]
 .Prerequisites
 
@@ -205,16 +212,9 @@ spec:
         hybridClusterNetwork: <1>
         - cidr: 10.132.0.0/14
           hostPrefix: 23
-        hybridOverlayVXLANPort: 9898 <2>
 ----
 <1> Specify the CIDR configuration used for nodes on the additional overlay network. The `hybridClusterNetwork` CIDR must not overlap with the `clusterNetwork` CIDR.
-<2> Specify a custom VXLAN port for the additional overlay network. This is required for running Windows nodes in a cluster installed on vSphere, and must not be configured for any other cloud provider. The custom port can be any open port excluding the default `4789` port. For more information on this requirement, see the Microsoft documentation on link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/common-problems#pod-to-pod-connectivity-between-hosts-is-broken-on-my-kubernetes-cluster-running-on-vsphere[Pod-to-pod connectivity between hosts is broken].
 --
-+
-[NOTE]
-====
-Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019 is not supported on clusters with a custom `hybridOverlayVXLANPort` value because this Windows server version does not support selecting a custom VXLAN port.
-====
 
 . Save the `cluster-network-03-config.yml` file and quit the text editor.
 . Optional: Back up the `manifests/cluster-network-03-config.yml` file. The
@@ -246,8 +246,7 @@ $ oc patch networks.operator.openshift.io cluster --type=merge \
                 "cidr": "<cidr>",
                 "hostPrefix": <prefix>
               }
-            ],
-            "hybridOverlayVXLANPort": <overlay_port>
+            ]
           }
         }
       }
@@ -260,12 +259,6 @@ where:
 
 `cidr`:: Specify the CIDR configuration used for nodes on the additional overlay network. This CIDR must not overlap with the cluster network CIDR.
 `hostPrefix`:: Specifies the subnet prefix length to assign to each individual node. For example, if `hostPrefix` is set to `23`, then each node is assigned a `/23` subnet out of the given `cidr`, which allows for 510 (2^(32 - 23) - 2) pod IP addresses. If you are required to provide access to nodes from an external network, configure load balancers and routers to manage the traffic.
-`hybridOverlayVXLANPort`:: Specify a custom VXLAN port for the additional overlay network. This is required for running Windows nodes in a cluster installed on vSphere, and must not be configured for any other cloud provider. The custom port can be any open port excluding the default `4789` port. For more information on this requirement, see the Microsoft documentation on link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/common-problems#pod-to-pod-connectivity-between-hosts-is-broken-on-my-kubernetes-cluster-running-on-vsphere[Pod-to-pod connectivity between hosts is broken].
-
-[NOTE]
-====
-Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019 is not supported on clusters with a custom `hybridOverlayVXLANPort` value because this Windows server version does not support selecting a custom VXLAN port.
-====
 --
 +
 .Example output
@@ -280,6 +273,7 @@ network.operator.openshift.io/cluster patched
 ----
 $ oc get network.operator.openshift.io -o jsonpath="{.items[0].spec.defaultNetwork.ovnKubernetesConfig}"
 ----
+
 endif::post-install[]
 ////
 

networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc

@@ -14,10 +14,7 @@ include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]
 [id="configuring-hybrid-networking-additional-resources"]
 == Additional resources
 
-////
-Hiding until WMCO 10.19.0 GAs
-* ../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads]
-* ../../windows_containers/enabling-windows-container-workloads.adoc#enabling-windows-container-workloads[Enabling Windows container workloads]
-////
+* xref:../../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[Understanding Windows container workloads]
+* xref:../../windows_containers/enabling-windows-container-workloads.adoc#enabling-windows-container-workloads[Enabling Windows container workloads]
 * xref:../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[Installing a cluster on AWS with network customizations]
 * xref:../../installing/installing_azure/ipi/installing-azure-network-customizations.adoc#installing-azure-network-customizations[Installing a cluster on Azure with network customizations]

welcome/learn_more_about_openshift.adoc

@@ -170,13 +170,10 @@ a|* xref:../networking/networking_operators/cluster-network-operator.adoc#nw-clu
 | xref:../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[Manage Operators]
 | xref:../operators/user/olm-creating-apps-from-installed-operators.adoc#olm-creating-apps-from-installed-operators[Creating applications from installed Operators]
 
-|===
-
-//// 
-Hiding until WMCO 10.19.0 releases, replace as the last row of the above table after WMCO GAs
 | xref:../windows_containers/index.adoc#index[{productwinc} overview]
-| windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads_understanding-windows-container-workloads[Understanding Windows container workloads]
-////
+| xref:../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads_understanding-windows-container-workloads[Understanding Windows container workloads]
+
+|===
 
 [discrete]
 ==== Changing cluster components