Skip to content

Commit c8dc55d

Browse files
author
Michael Burke
committed
WMCO 10.17.1 Release Notes
1 parent 7210823 commit c8dc55d

File tree

5 files changed

+62
-38
lines changed

5 files changed

+62
-38
lines changed

‎_topic_maps/_topic_map.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2824,8 +2824,8 @@ Topics:
28242824
Topics:
28252825
- Name: Red Hat OpenShift support for Windows Containers release notes
28262826
File: windows-containers-release-notes-10-17-x
2827-
# - Name: Past releases
2828-
# File: windows-containers-release-notes-10-17-x-past
2827+
- Name: Past releases
2828+
File: windows-containers-release-notes-10-17-x-past
28292829
- Name: Windows Machine Config Operator prerequisites
28302830
File: windows-containers-release-notes-10-17-x-prereqs
28312831
- Name: Windows Machine Config Operator known limitations

‎modules/windows-containers-release-notes-10-17-0.adoc

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * windows_containers/wmco_rn/windows-containers-release-notes-10-17-x-past.adoc
4+
5+
6+
:_mod-docs-content-type: CONCEPT
7+
[id="windows-containers-release-notes-10-17-0_{context}"]
8+
= Release notes for Red Hat Windows Machine Config Operator 10.17.0
9+
10+
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].
11+
12+
[id="wmco-10-17-0-new-features"]
13+
== New features and improvements
14+
15+
[id="wmco-10-17-0-new-features-kubernetes"]
16+
=== Kubernetes upgrade
17+
18+
The WMCO now uses Kubernetes 1.30.
19+
20+
[id="wmco-10-17-0-bug-fixes"]
21+
== Bug fixes
22+
23+
* 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*])
24+
25+
// Copied from 4.16 release notes.
26+
* 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*])
27+
28+
// Copied from 4.16 release notes.
29+
* 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*])

‎modules/windows-containers-release-notes-10-17-1.adoc

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * windows_containers/wmco_rn/windows-containers-release-notes-10-17-x.adoc
4+
5+
:_mod-docs-content-type: CONCEPT
6+
[id="windows-containers-release-notes-10-17-1_{context}"]
7+
= Release notes for Red Hat Windows Machine Config Operator 10.17.1
8+
9+
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].
10+
11+
[id="wmco-10-17-1-new-features"]
12+
== New features and improvements
13+
14+
[id="wmco-10-17-1-new-features-debuglogging"]
15+
=== WMCO now defaults to info-level logging
16+
The WMCO is configured to use the `info` log level by default. You can change the log level to `debug` by editing the WMCO subscription object.
17+
// Based on https://issues.redhat.com/browse/WINC-1345
18+
////
19+
For more information, see xref: ../../windows_containers/enabling-windows-container-workloads.adoc#wmco-configure-debug-logging_enabling-windows-container-workloads[Configuring debug-level logging for the Windows Machine Config Operator].
20+
Merge https://github.com/openshift/openshift-docs/pull/93958 upon release of WMCO 10.17.1 to add the linked module.
21+
////
22+
23+
[id="wmco-10-17-1-bug-fixes"]
24+
== Bug fixes
25+
26+
* Previously, Windows nodes were unable to pull from image mirror registries if an organization name or namespace was included in the source of the `ImageTagMirrorSet` (ITMS) object. With this fix, you can include an organization name or namespace in the `ITMS` object. With this change, additional guidelines and requirements around using mirror registries have been added to the {product-title} documentation. (link:https://issues.redhat.com/browse/OCPBUGS-55915[*OCPBUGS-55915*])
27+
// The "additional guidelines and requirements" are forthcoming in https://github.com/openshift/openshift-docs/pull/93939
28+
29+
* 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]. (link:https://issues.redhat.com/browse/OCPBUGS-44237[*OCPBUGS-44237*])

‎windows_containers/wmco_rn/windows-containers-release-notes-10-17-x-past.adoc

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,16 +10,4 @@ The following release notes are for previous versions of the Windows Machine Con
1010

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

13-
[id="wmco-10-17-"]
14-
== Release notes for Red Hat Windows Machine Config Operator 10.17.0
15-
16-
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
17-
18-
19-
[id="wmco-10-17-past-new-features"]
20-
=== New features and improvements
21-
22-
[id="wmco-10-17-bug-fixes"]
23-
=== Bug fixes
24-
25-
13+
include::modules/windows-containers-release-notes-10-17-0.adoc[leveloffset=+1]

‎windows_containers/wmco_rn/windows-containers-release-notes-10-17-x.adoc

Lines changed: 1 addition & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -6,27 +6,5 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
include::modules/windows-containers-release-notes-10-17-1.adoc[leveloffset=+1]
910

10-
[id="wmco-10-17-0"]
11-
== Release notes for Red Hat Windows Machine Config Operator 10.17.0
12-
13-
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].
14-
15-
[id="wmco-10-17-0-new-features"]
16-
=== New features and improvements
17-
18-
[id="wmco-10-17-0-new-features-kubernetes"]
19-
==== Kubernetes upgrade
20-
21-
The WMCO now uses Kubernetes 1.30.
22-
23-
[id="wmco-10-17-0-bug-fixes"]
24-
=== Bug fixes
25-
26-
* 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*])
27-
28-
// Copied from 4.16 release notes.
29-
* 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*])
30-
31-
// Copied from 4.16 release notes.
32-
* 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*])

0 commit comments

Comments
 (0)