Skip to content

WMCO 10.17.1 Release Notes #84675

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.

Sign up for GitHub

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 1 commit into
base: enterprise-4.17
Choose a base branch
from
Open

WMCO 10.17.1 Release Notes #84675

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions _topic_maps/_topic_map.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2824,8 +2824,8 @@ Topics:
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: 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
Expand Down
22 changes: 17 additions & 5 deletions windows_containers/wmco_rn/windows-containers-release-notes-10-17-x-past.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,16 +10,28 @@ The following release notes are for previous versions of the Windows Machine Con

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

[id="wmco-10-17-"]
[id="wmco-10-17-0"]
== Release notes for Red Hat Windows Machine Config Operator 10.17.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.17.0 were released in link:https://access.redhat.com/errata/RHSA-2024:7436[RHSA-2024:7436].


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

[id="wmco-10-17-bug-fixes"]
[id="wmco-10-17-0-new-features-kubernetes"]
==== Kubernetes upgrade

The WMCO now uses Kubernetes 1.30.

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

* Previously, if a Windows VM had its PowerShell `ExecutionPolicy` set to `Restricted`, the Windows Instance Config Daemon (WICD) could not run the commands on that VM that are necessary for creating Windows nodes. With this fix, the WICD now bypasses the execution policy on the VM when running PowerShell commands. As a result, the WICD can create Windows nodes on the VM as expected. (link:https://issues.redhat.com/browse/OCPBUGS-30995[*OCPBUGS-30995*])

// Copied from 4.16 release notes.
* Previously, if reverse DNS lookup failed due to an error, such as the reverse DNS lookup services being unavailable, the WMCO would not fall back to using the VM hostname to determine if a certificate signing requests (CSR) should be approved. As a consequence, Bring-Your-Own-Host (BYOH) Windows nodes configured with an IP address would not become available. With this fix, BYOH nodes are properly added if reverse DNS is not available. (link:https://issues.redhat.com/browse/OCPBUGS-36643[*OCPBUGS-36643*])

// Copied from 4.16 release notes.
* Previously, if there were multiple service account token secrets in the WMCO namespace, scaling Windows nodes would fail. With this fix, the WMCO uses only the secret it creates, ignoring any other service account token secrets in the WMCO namespace. As a result, Windows nodes scale properly. (link:https://issues.redhat.com/browse/OCPBUGS-29253[*OCPBUGS-29253*])


24 changes: 5 additions & 19 deletions windows_containers/wmco_rn/windows-containers-release-notes-10-17-x.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,26 +7,12 @@ include::_attributes/common-attributes.adoc[]
toc::[]


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

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 link:https://access.redhat.com/errata/RHSA-2024:TBD[RHSA-2024:TBD].
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.1 were released in link:https://access.redhat.com/errata/RHSA-2024:TBD[RHSA-2024:TBD].

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

[id="wmco-10-17-0-new-features-kubernetes"]
==== Kubernetes upgrade

The WMCO now uses Kubernetes 1.30.

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

* Previously, if a Windows VM had its PowerShell `ExecutionPolicy` set to `Restricted`, the Windows Instance Config Daemon (WICD) could not run the commands on that VM that are necessary for creating Windows nodes. With this fix, the WICD now bypasses the execution policy on the VM when running PowerShell commands. As a result, the WICD can create Windows nodes on the VM as expected. (link:https://issues.redhat.com/browse/OCPBUGS-30995[*OCPBUGS-30995*])

// Copied from 4.16 release notes.
* Previously, if reverse DNS lookup failed due to an error, such as the reverse DNS lookup services being unavailable, the WMCO would not fall back to using the VM hostname to determine if a certificate signing requests (CSR) should be approved. As a consequence, Bring-Your-Own-Host (BYOH) Windows nodes configured with an IP address would not become available. With this fix, BYOH nodes are properly added if reverse DNS is not available. (link:https://issues.redhat.com/browse/OCPBUGS-36643[*OCPBUGS-36643*])

// Copied from 4.16 release notes.
* Previously, if there were multiple service account token secrets in the WMCO namespace, scaling Windows nodes would fail. With this fix, the WMCO uses only the secret it creates, ignoring any other service account token secrets in the WMCO namespace. As a result, Windows nodes scale properly. (link:https://issues.redhat.com/browse/OCPBUGS-29253[*OCPBUGS-29253*])
* Previously, the {product-title} documentation lacked information about WMCO support for the installer-provisioned infrastructure (IPI) and the user-provisioned infrastructure (UPI) installation methods. With this fix, the documentation reports that the IPI method is the preferred installation method and can be used with all platforms. The UPI method is limited to specific use cases. For more information, see xref:../../windows_containers/wmco_rn/windows-containers-release-notes-10-17-x-prereqs.adoc#wmco-prerequisites-supported-install-10.17.0_windows-containers-release-notes-10-17-x-prereqs[WMCO supported installation method].