openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

WMCO 10.15.2 release notes

Browse Source
This commit is contained in:
Michael Burke
2024-04-12 10:49:29 -04:00
parent 140ee2f342
commit c07edc4de1
10 changed files with 69 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
_topic_maps/_topic_map.yml
View File

@@ -2584,8 +2584,16 @@ Distros: openshift-origin,openshift-enterprise
Topics:
- Name: Red Hat OpenShift support for Windows Containers overview
File: index
- Name: Red Hat OpenShift support for Windows Containers release notes
File: windows-containers-release-notes-10-15-x
- Name: Release notes
Dir: wmco_rn
Topics:
- Name: Red Hat OpenShift support for Windows Containers release notes
File: windows-containers-release-notes-10-15-x
- Name: Past releases
File: windows-containers-release-notes-10-15-x-past
- 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

2
windows_containers/index.adoc
View File

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
{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/windows-containers-release-notes-10-15-x.adoc#windows-containers-release-notes-10-15-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/windows-rn/windows-containers-release-notes-10-15-x.adoc#windows-containers-release-notes-10-15-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].

2
windows_containers/understanding-windows-container-workloads.adoc
View File

@@ -27,6 +27,6 @@ include::modules/windows-workload-management.adoc[leveloffset=+1]
include::modules/windows-node-services.adoc[leveloffset=+1]
include::modules/windows-containers-release-notes-limitations.adoc[leveloffset=+1]
// include::modules/windows-containers-release-notes-limitations.adoc[leveloffset=+1]
//modules/windows-linux-containers-differences.adoc[leveloffset=+1]

18
windows_containers/windows-containers-support.adoc Normal file
View File

@@ -0,0 +1,18 @@
:_mod-docs-content-type: ASSEMBLY
[id="windows-containers-support"]
= Getting support
include::_attributes/common-attributes.adoc[]
:context: understanding-windows-container-workloads
toc::[]
// wording taken and modified from https://access.redhat.com/support/policy/updates/openshift#windows
Windows Container Support for Red{nbsp}Hat OpenShift is provided and available as an optional, installable component. Windows Container Support for Red{nbsp}Hat OpenShift is not part of the {product-title} subscription. It requires an additional Red{nbsp}Hat subscription and is supported according to the link:https://access.redhat.com/support/offerings/production/soc/[Scope of coverage] and link:https://access.redhat.com/support/offerings/production/sla[Service level agreements].
You must have this separate subscription to receive support for Windows Container Support for Red{nbsp}Hat OpenShift. Without this additional Red{nbsp}Hat subscription, deploying Windows container workloads in production clusters is not supported. You can request support through the link:http://access.redhat.com/[Red{nbsp}Hat Customer Portal].
For more information, see the Red{nbsp}Hat OpenShift Container Platform Life Cycle Policy document for link:https://access.redhat.com/support/policy/updates/openshift#windows[{productwinc}].
If you do not have this additional Red{nbsp}Hat subscription, you can use the Community Windows Machine Config Operator, a distribution that lacks official support.

1
windows_containers/wmco_rn/_attributes Symbolic link
View File

@@ -0,0 +1 @@
../../_attributes/

1
windows_containers/wmco_rn/images Symbolic link
View File

@@ -0,0 +1 @@
../../images/

1
windows_containers/wmco_rn/modules Symbolic link
View File

@@ -0,0 +1 @@
../../modules/

1
windows_containers/wmco_rn/snippets Symbolic link
View File

@@ -0,0 +1 @@
../../snippets/

51
windows_containers/windows-containers-release-notes-10-15-x.adoc → windows_containers/wmco_rn/windows-containers-release-notes-10-15-x-past.adoc
View File

@@ -1,51 +1,12 @@
:_mod-docs-content-type: ASSEMBLY
[id="windows-containers-release-notes-10-15-x"]
= {productwinc} release notes
:context: windows-containers-release-notes-10-15-x-past
[id="nodes-cma-autoscaling-custom-rn-past"]
= Release notes for past releases of the Windows Machine Config Operator
include::_attributes/common-attributes.adoc[]
:context: windows-containers-release-notes
toc::[]
[id="about-windows-containers"]
== About {productwinc}
Windows Container Support for Red{nbsp}Hat OpenShift enables running Windows compute nodes in an {product-title} cluster. Running Windows workloads is possible by using the Red{nbsp}Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With Windows nodes available, you can run Windows container workloads in {product-title}.
The release notes for Red{nbsp}Hat OpenShift for Windows Containers tracks the development of the WMCO, which provides all Windows container workload capabilities in {product-title}.
ifndef::openshift-origin[]
[id="getting-support"]
== Getting support
// wording taken and modified from https://access.redhat.com/support/policy/updates/openshift#windows
Windows Container Support for Red{nbsp}Hat OpenShift is provided and available as an optional, installable component. Windows Container Support for Red{nbsp}Hat OpenShift is not part of the {product-title} subscription. It requires an additional Red{nbsp}Hat subscription and is supported according to the link:https://access.redhat.com/support/offerings/production/soc/[Scope of coverage] and link:https://access.redhat.com/support/offerings/production/sla[Service level agreements].
You must have this separate subscription to receive support for Windows Container Support for Red{nbsp}Hat OpenShift. Without this additional Red{nbsp}Hat subscription, deploying Windows container workloads in production clusters is not supported. You can request support through the link:http://access.redhat.com/[Red{nbsp}Hat Customer Portal].
For more information, see the Red{nbsp}Hat OpenShift Container Platform Life Cycle Policy document for link:https://access.redhat.com/support/policy/updates/openshift#windows[{productwinc}].
If you do not have this additional Red{nbsp}Hat subscription, you can use the Community Windows Machine Config Operator, a distribution that lacks official support.
endif::openshift-origin[]
[id="about-windows-containers-numbering"]
== WMCO numbering
Starting with this release, y-stream releases of the WMCO will be in step with {product-title}, with only z-stream releases between {product-title} releases. The WMCO numbering reflects the associated {product-title} version in the y-stream position. For example, the current release of WMCO is associated with {product-title} version 4.15. Thus, the numbering is WMCO 10.15.z.
[id="wmco-10-15-2"]
== Release notes for Red{nbsp}Hat Windows Machine Config Operator 10.15.2
This release of the WMCO provides new features and bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 10.15.2 were released in link:https://access.redhat.com/errata/RHBA-2024:2704[RHBA-2024:2704].
[id="wmco-10-15-2-bug-fixes"]
=== Bug fixes
* Previously, on Azure clusters the WMCO would check if an external cloud controller (CCM) was being used on the cluster. CCM use is the default. If a CCM is being used, the Operator would adjust configuration logic accordingly. Because the status condition that the WMCO used to check for the CCM has been removed, the WMCO acted as if a CCM was not in use. This fix removes the check. As a result, the WMCO always configures the required logic on Azure clusters.
* Previously, the kubelet was unable to authenticate with private ECR registries. Because of this error, the kubelet was not able to pull images from these registries. With this fix, the kubelet is able to pull images from these registries as expected. (link:https://issues.redhat.com/browse/OCPBUGS-26602[*OCPBUGS-26602*])
* Previously, the WMCO was logging error messages when any commands being run through an SSH connection to a Windows instance failed. This was incorrect behavior, because some commands are expected to fail. For example, when WMCO reboots a node, the Operator runs PowerShell commands on the instance until they fail, meaning the SSH connection rebooted as expected. With this fix, only actualy errors are now logged. (link:https://issues.redhat.com/browse/OCPBUGS-20255[*OCPBUGS-20255*])
The following release notes are for previous versions of the Windows Machine Config Operator (WMCO).
[id="wmco-10-15-1"]
== Release notes for Red{nbsp}Hat Windows Machine Config Operator 10.15.1
@@ -96,7 +57,3 @@ The WMCO now uses Kubernetes 1.28.
// Also in 7.2.1, 8.1.2
* Previously, because of bad logic in the networking configuration script, the WICD was incorrectly reading carriage returns in the CNI configuration file as changes, and identified the file as modified. This caused the CNI configuration to be unnecessarily reloaded, potentially resulting in container restarts and brief network outages. With this fix, the WICD now reloads the CNI configuration only when the CNI configuration is actually modified. (link:https://issues.redhat.com/browse/OCPBUGS-25756[*OCPBUGS-25756*])
include::modules/wmco-prerequisites.adoc[leveloffset=+1]
include::modules/windows-containers-release-notes-limitations.adoc[leveloffset=+1]

31
windows_containers/wmco_rn/windows-containers-release-notes-10-15-x.adoc Normal file
View File

@@ -0,0 +1,31 @@
:_mod-docs-content-type: ASSEMBLY
[id="windows-containers-release-notes-10-15-x"]
= {productwinc} release notes
include::_attributes/common-attributes.adoc[]
:context: windows-containers-release-notes
toc::[]
The release notes for Red{nbsp}Hat OpenShift for Windows Containers tracks the development of the Windows Machine Config Operator (WMCO), which provides all Windows container workload capabilities in {product-title}.
[id="about-windows-containers-numbering"]
== Windows Machine Config Operator numbering
Starting with this release, y-stream releases of the WMCO will be in step with {product-title}, with only z-stream releases between {product-title} releases. The WMCO numbering reflects the associated {product-title} version in the y-stream position. For example, the current release of WMCO is associated with {product-title} version 4.15. Thus, the numbering is WMCO 10.15.z.
[id="wmco-10-15-2"]
== Release notes for Red{nbsp}Hat Windows Machine Config Operator 10.15.2
This release of the WMCO provides new features and bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 10.15.2 were released in link:https://access.redhat.com/errata/RHBA-2024:2704[RHBA-2024:2704].
[id="wmco-10-15-2-bug-fixes"]
=== Bug fixes
* Previously, on Azure clusters the WMCO would check if an external Cloud Controller Manager (CCM) was being used on the cluster. CCM use is the default. If a CCM is being used, the Operator would adjust configuration logic accordingly. Because the status condition that the WMCO used to check for the CCM was removed, the WMCO proceeded as if a CCM was not in use. This fix removes the check. As a result, the WMCO always configures the required logic on Azure clusters. (link:https://issues.redhat.com/browse/OCPBUGS-31704[*OCPBUGS-31704*])
* Previously, the kubelet was unable to authenticate with private Elastic Container Registries (ECR) registries. Because of this error, the kubelet was not able to pull images from these registries. With this fix, the kubelet is able to pull images from these registries as expected. (link:https://issues.redhat.com/browse/OCPBUGS-26602[*OCPBUGS-26602*])
* Previously, the WMCO was logging error messages when any commands being run through an SSH connection to a Windows instance failed. This was incorrect behavior because some commands are expected to fail. For example, when WMCO reboots a node the Operator runs PowerShell commands on the instance until they fail, meaning the SSH connection rebooted as expected. With this fix, only actualy errors are now logged. (link:https://issues.redhat.com/browse/OCPBUGS-20255[*OCPBUGS-20255*])
include::modules/windows-containers-release-notes-limitations.adoc[leveloffset=+1]