diff --git a/_topic_maps/_topic_map.yml b/_topic_maps/_topic_map.yml index 3a81361f9c..5cb3998a50 100644 --- a/_topic_maps/_topic_map.yml +++ b/_topic_maps/_topic_map.yml @@ -2820,13 +2820,13 @@ Topics: # Dir: wmco_rn # Topics: # - Name: Red Hat OpenShift support for Windows Containers release notes -# File: windows-containers-release-notes-10-17-x +# File: windows-containers-release-notes-10-19-x # - Name: Past releases -# File: windows-containers-release-notes-10-17-x-past +# File: windows-containers-release-notes-10-19-x-past # - Name: Windows Machine Config Operator prerequisites -# File: windows-containers-release-notes-10-17-x-prereqs +# File: windows-containers-release-notes-10-19-x-prereqs # - Name: Windows Machine Config Operator known limitations -# File: windows-containers-release-notes-10-17-x-limitations +# File: windows-containers-release-notes-10-19-x-limitations #- Name: Getting support # File: windows-containers-support # Distros: openshift-enterprise diff --git a/installing/installing_aws/ipi/installing-aws-network-customizations.adoc b/installing/installing_aws/ipi/installing-aws-network-customizations.adoc index 81bf34e67d..c147d5d76c 100644 --- a/installing/installing_aws/ipi/installing-aws-network-customizations.adoc +++ b/installing/installing_aws/ipi/installing-aws-network-customizations.adoc @@ -110,7 +110,7 @@ include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+1] include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1] //// -Hiding until WMCO 10.18.0 GAs +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]. diff --git a/installing/installing_azure/ipi/installing-azure-network-customizations.adoc b/installing/installing_azure/ipi/installing-azure-network-customizations.adoc index 6e4d03225a..5ebc0a92e9 100644 --- a/installing/installing_azure/ipi/installing-azure-network-customizations.adoc +++ b/installing/installing_azure/ipi/installing-azure-network-customizations.adoc @@ -47,7 +47,7 @@ include::modules/nw-operator-cr.adoc[leveloffset=+1] include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1] //// -Hiding until WMCO 10.18.0 GAs +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]. diff --git a/installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc b/installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc index eb496de661..49da257811 100644 --- a/installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc +++ b/installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc @@ -51,7 +51,7 @@ include::modules/nw-operator-cr.adoc[leveloffset=+1] include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1] //// -Hiding until WMCO 10.18.0 GAs +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]. diff --git a/installing/overview/installing-preparing.adoc b/installing/overview/installing-preparing.adoc index b34abb4255..d0e54fed2f 100644 --- a/installing/overview/installing-preparing.adoc +++ b/installing/overview/installing-preparing.adoc @@ -118,7 +118,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.18.0 GAs +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. //// diff --git a/modules/configuring-hybrid-ovnkubernetes.adoc b/modules/configuring-hybrid-ovnkubernetes.adoc index 7707efad63..290307695d 100644 --- a/modules/configuring-hybrid-ovnkubernetes.adoc +++ b/modules/configuring-hybrid-ovnkubernetes.adoc @@ -16,7 +16,7 @@ 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.18.0 GAs +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. @@ -26,7 +26,7 @@ This configuration is necessary to run both Linux and Windows nodes in the same ifndef::post-install[] .Prerequisites -// Made changes to hide Windows-related material until WMCO 4.18.0 releases. Below is the full procedure, commented out. +// 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. @@ -147,7 +147,7 @@ $ oc get network.operator.openshift.io -o jsonpath="{.items[0].spec.defaultNetwo endif::post-install[] //// -Hiding until WMCO 10.18.0 GAs +Hiding until WMCO 10.19.0 GAs. Swap the two sections after WMCO GA. ifndef::post-install[] .Prerequisites @@ -261,6 +261,11 @@ 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 @@ -275,16 +280,6 @@ network.operator.openshift.io/cluster patched ---- $ oc get network.operator.openshift.io -o jsonpath="{.items[0].spec.defaultNetwork.ovnKubernetesConfig}" ---- - - -//// -Hiding until WMCO 10.16 GAs. Replace in step 1 after `where:` list -[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. -==== -//// - endif::post-install[] //// diff --git a/networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc b/networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc index f49a7a7b8e..c908375cb5 100644 --- a/networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc +++ b/networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.adoc @@ -15,7 +15,7 @@ include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1] == Additional resources //// -Hiding until WMCO 10.18.0 GAs +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] //// diff --git a/welcome/learn_more_about_openshift.adoc b/welcome/learn_more_about_openshift.adoc index 7ec2bfc75a..1d600ed26f 100644 --- a/welcome/learn_more_about_openshift.adoc +++ b/welcome/learn_more_about_openshift.adoc @@ -175,9 +175,9 @@ a|* xref:../networking/networking_operators/cluster-network-operator.adoc#nw-clu |=== //// -Hiding until WMCO 10.18.0 releases, replace as the last row of the above table after WMCO GAs -| xref: ../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads_understanding-windows-container-workloads[Understanding Windows container workloads] -| +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] //// [discrete] diff --git a/windows_containers/index.adoc b/windows_containers/index.adoc index f2ce1808b2..7451ff946e 100644 --- a/windows_containers/index.adoc +++ b/windows_containers/index.adoc @@ -10,8 +10,8 @@ toc::[] Documentation for {productwinc} is planned to be available for {product-title} {product-version} in the near future. //// -Hiding until WMCO 10.18.0 GAs -{productwinc} 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}. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the xref:../windows_containers/wmco_rn/windows-containers-release-notes-10-17-x.adoc#windows-containers-release-notes-10-17-x[release notes]. +Hiding until WMCO 10.19.0 GAs +{productwinc} 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}. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the xref:../windows_containers/wmco_rn/windows-containers-release-notes-10-19-x.adoc#windows-containers-release-notes-10-19-x[release notes]. You can add Windows nodes either by creating a xref:../windows_containers/creating_windows_machinesets/creating-windows-machineset-aws.adoc#creating-windows-machineset-aws[compute machine set] or by specifying existing Bring-Your-Own-Host (BYOH) Window instances through a xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[configuration map].