Skip to content

WMCO 10.19.0 release notes #93968

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: enterprise-4.19
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
80 changes: 40 additions & 40 deletions _topic_maps/_topic_map.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2898,47 +2898,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: Release notes
Dir: wmco_rn
Topics:
- Name: Red Hat OpenShift support for Windows Containers release notes
File: windows-containers-release-notes-10-19-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
# File: windows-containers-release-notes-10-19-x-past
- Name: Windows Machine Config Operator prerequisites
File: windows-containers-release-notes-10-19-x-prereqs
- Name: Windows Machine Config Operator known limitations
File: windows-containers-release-notes-10-19-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
Expand Down
2 changes: 1 addition & 1 deletion release_notes/addtl-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ xref:../observability/otel/otel-rn.adoc#otel-rn[{OTELName}]

////
Hiding until
xref:../windows_containers/wmco_rn/windows-containers-release-notes-10-17-x.adoc#windows-containers-release-notes-10-17-x[{productwinc}] +
xref:../windows_containers/wmco_rn/windows-containers-release-notes-10-19-x.adoc#windows-containers-release-notes-10-19-x[{productwinc}] +
{nbsp} +
////

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Windows instances deployed by the WMCO are configured with the containerd contai

[role="_additional-resources"]
.Additional resources
* For the comprehensive prerequisites for the Windows Machine Config Operator, see xref:../windows_containers/wmco_rn/windows-containers-release-notes-10-17-x-prereqs.adoc#windows-containers-release-notes-10-17-x-prereqs[Windows Machine Config Operator prerequisites].
* For the comprehensive prerequisites for the Windows Machine Config Operator, see xref:../windows_containers/wmco_rn/windows-containers-release-notes-10-19-x-prereqs.adoc#windows-containers-release-notes-10-19-x-prereqs[Windows Machine Config Operator prerequisites].

[id="installing-the-wmco"]
== Installing the Windows Machine Config Operator
Expand Down
2 changes: 1 addition & 1 deletion windows_containers/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Documentation for {productwinc} is planned to be available for {product-title} {

////
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].
{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].

Expand Down

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
:_mod-docs-content-type: ASSEMBLY
:context: windows-containers-release-notes-10-17-x-limitations
[id="windows-containers-release-notes-10-17-x-limitations"]
:context: windows-containers-release-notes-10-19-x-limitations
[id="windows-containers-release-notes-10-19-x-limitations"]
= Windows Machine Config Operator known limitations
include::_attributes/common-attributes.adoc[]

Expand Down
Original file line number Diff line number Diff line change
@@ -1,25 +1,24 @@
:_mod-docs-content-type: ASSEMBLY
:context: windows-containers-release-notes-10-17-x-past
[id="windows-containers-release-notes-10-17-x-past"]
:context: windows-containers-release-notes-10-19-x-past
[id="windows-containers-release-notes-10-19-x-past"]
= Release notes for past releases of the Windows Machine Config Operator
include::_attributes/common-attributes.adoc[]

toc::[]

The following release notes are for previous versions of the Windows Machine Config Operator (WMCO).

For the current version, see xref:../../windows_containers/wmco_rn/windows-containers-release-notes-10-17-x.adoc#windows-containers-release-notes-10-17-x[{productwinc} release notes].
For the current version, see xref:../../windows_containers/wmco_rn/windows-containers-release-notes-10-19-x.adoc#windows-containers-release-notes-10-19-x[{productwinc} release notes].

[id="wmco-10-17-"]
== Release notes for Red Hat Windows Machine Config Operator 10.17.0
[id="wmco-10-19-0"]
== Release notes for Red Hat Windows Machine Config Operator 10-19.0

This release of the WMCO provides bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 10.17.0 were released in
This release of the WMCO provides bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 10-19.0 were released in


[id="wmco-10-17-past-new-features"]
[id="wmco-10-19-past-new-features"]
=== New features and improvements

[id="wmco-10-17-bug-fixes"]
[id="wmco-10-19-bug-fixes"]
=== Bug fixes


Original file line number Diff line number Diff line change
@@ -1,22 +1,22 @@
:_mod-docs-content-type: ASSEMBLY
:context: windows-containers-release-notes-10-17-x-prereqs
[id="windows-containers-release-notes-10-17-x-prereqs"]
:context: windows-containers-release-notes-10-19-x-prereqs
[id="windows-containers-release-notes-10-19-x-prereqs"]
= Windows Machine Config Operator prerequisites
include::_attributes/common-attributes.adoc[]

The following information details the supported platform versions, Windows Server versions, and networking configurations for the Windows Machine Config Operator (WMCO). See the vSphere documentation for any information that is relevant to only that platform.

[id="wmco-prerequisites-supported-install-10.17.0_{context}"]
[id="wmco-prerequisites-supported-install-10-19.0_{context}"]
== WMCO supported installation method

The WMCO fully supports installing Windows nodes into installer-provisioned infrastructure (IPI) clusters. This is the preferred {product-title} installation method.

For user-provisioned infrastructure (UPI) clusters, the WMCO supports installing Windows nodes only into a UPI cluster installed with the `platform: none` field set in the `install-config.yaml` file (bare-metal or provider-agnostic) and only for the xref:../../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[BYOH (Bring Your Own Host)] use case. UPI is not supported for any other platform.

[id="wmco-prerequisites-supported-10.17.0_{context}"]
== WMCO 10.17.0 supported platforms and Windows Server versions
[id="wmco-prerequisites-supported-10-19.0_{context}"]
== WMCO 10-19.0 supported platforms and Windows Server versions

The following table lists the link:https://docs.microsoft.com/en-us/windows/release-health/windows-server-release-info[Windows Server versions] that are supported by WMCO 10.17.0, based on the applicable platform. Windows Server versions not listed are not supported and attempting to use them will cause errors. To prevent these errors, use only an appropriate version for your platform.
The following table lists the link:https://docs.microsoft.com/en-us/windows/release-health/windows-server-release-info[Windows Server versions] that are supported by WMCO 10-19.0, based on the applicable platform. Windows Server versions not listed are not supported and attempting to use them will cause errors. To prevent these errors, use only an appropriate version for your platform.

[cols="3,7",options="header"]
|===
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
:_mod-docs-content-type: ASSEMBLY
[id="windows-containers-release-notes-10-19-x"]
= {productwinc} release notes
include::_attributes/common-attributes.adoc[]
:context: windows-containers-release-notes

toc::[]


[id="wmco-10-19-0"]
== Release notes for Red Hat Windows Machine Config Operator 10-19.0

This release of the WMCO provides bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 10-19.0 were released in


[id="wmco-10-19-0-new-features"]
=== New features and improvements

[id="wmco-10-19-0-new-features-debuglogging"]
==== WMCO kubelet configuration changes
// https://github.com/openshift/windows-machine-config-operator/pull/2709

With this release, the WMCO now sets the following values in the `KubeletConfig` custom resource (CR):

* The `system-reserved` parameter is now set to 2GiB of memory for system processes, as recommended in the link:https://kubernetes.io/docs/concepts/configuration/windows-resource-management/#resource-reservation[Kubernetes documentation].
* The `enforceNodeAllocatable` with a default value of `none`. Previously, the value was set to `[]` to avoid a known issue. Both settings disable the enforcement of node allocatable resource limits.
* The `evictionHard` parameters, `imagefs.available` and `nodefs.available` are now set to `15%` and `10%` respectively, as recommended in the link:https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals[Kubernetes documentation]

The `KubeletConfig` object configures the kubelet service, which runs on each node in the cluster to ensure that containers in a pod are running.

[id="wmco-10-19-0-bug-fixes"]
=== Bug fixes