WMCO 10.22.1 Release Notes - #116734
Open
mburke5678 wants to merge 1 commit into
Open
Conversation
openshift-ci
Bot
added
the
size/M
mburke5678
force-pushed
the
wmco-rn-10-22-1
branch
from
July 28, 2026 18:26
0b4e621 to
51f9376
Compare
| [role="_abstract"] | ||
| You can review the following release notes to learn about the new features and bug fixes in the Windows Machine Config Operator (WMCO) version 10.22.1. | ||
|
|
||
| The components of the WMCO version 10.22.1 were released in link:https://access.redhat.com/errata/RHBA-2026:TBD[RHBA-2026:TBD ]. |
Collaborator
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
jrvaldes
reviewed
Jul 28, 2026
| // Release notes for past versions; cut and paste current version to top of this file for next release | ||
| The following release notes are for previous versions of the Windows Machine Config Operator (WMCO). | ||
| [role="_abstract"] | ||
| You can review the following release notes to learn about changes in previous versions of the Custom Metrics Autoscaler Operator. |
Contributor
There was a problem hiding this comment.
Custom Metrics Autoscaler Operator
?
Contributor
Author
There was a problem hiding this comment.
Having a bad day ... week ... month....
jrvaldes
reviewed
Jul 28, 2026
| Issued: 28 July 2026 | ||
|
|
||
| [role="_abstract"] | ||
| You can review the following release notes to learn about the new features and bug fixes in the Windows Machine Config Operator (WMCO) version 10.22.1. |
Contributor
There was a problem hiding this comment.
new features
no new features in this release, just bug and CVE fixes
Contributor
Author
There was a problem hiding this comment.
Sorry. Bad copy/paste. And a lack of proofread so far.
|
|
||
| == Bug and CVE fixes | ||
|
|
||
| * Before this update, the SSH connection between the WMCO and a Windows node would terminate when the WMCO rebooted the node after a configuration update. As a consequence, the WMCO incorrectly treated the SSH disconnection as a reboot failure, preventing the Windows node from completing required reboots. With this release, the reboot validation process is modified to ignore SSH termination errors and instead verify a successful reboot by using explicit node reachability checks and the SSH reconnection. As a result, Windows nodes successfully reboot upon node configuration changes. (link:https://issues.redhat.com/browse/OCPBUGS-98228[OCPBUGS-98228]/link:https://access.redhat.com/security/cve/cve-2026-54099[CVE-2026-54099]) |
Collaborator
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
|
|
||
| * Before this update, the SSH connection between the WMCO and a Windows node would terminate when the WMCO rebooted the node after a configuration update. As a consequence, the WMCO incorrectly treated the SSH disconnection as a reboot failure, preventing the Windows node from completing required reboots. With this release, the reboot validation process is modified to ignore SSH termination errors and instead verify a successful reboot by using explicit node reachability checks and the SSH reconnection. As a result, Windows nodes successfully reboot upon node configuration changes. (link:https://issues.redhat.com/browse/OCPBUGS-98228[OCPBUGS-98228]/link:https://access.redhat.com/security/cve/cve-2026-54099[CVE-2026-54099]) | ||
|
|
||
| * Before this update, when a Windows node or the Windows Instance Config Daemon (WICD) submitted a certificate signing requests (CSRs), the WMCO validated only that the certificate subject organization, for example `system:nodes` or `system:wicd-nodes`, appeared somewhere in the CSR subject. The validation did not require that organization be the only one listed. As a consequence, a CSR could have incorrectly passed validation with more than one organization listed. The WMCO approved and signed those CSRs, issuing certificates that did not strictly match the expected node identity constraints. With this release, the WMCO requires an exact single-organization match using `reflect.DeepEqual`, consistent with Kubelet client certificate validation in `isNodeClientCert()`. The CSR subject must contain exactly one organization, and it must match the expected group for the certificate type (WICD, kubelet client, or kubelet serving). As a result, CSRs with extra, missing, or incorrect organizations are rejected. Only CSRs with the exact expected organization are approved, preventing overly permissive certificate approval. (link:https://issues.redhat.com/browse/OCPBUGS-88343[OCPBUGS-88343]/link:https://access.redhat.com/security/cve/cve-2026-54100[CVE-2026-54100]) |
Collaborator
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
mburke5678
force-pushed
the
wmco-rn-10-22-1
branch
from
July 29, 2026 11:03
f8bfe73 to
7310864
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://redhat.atlassian.net/browse/OSDOCS-20939
Release notes for Red Hat Windows Machine Config Operator 10.22.1
Release notes for past releases of the Windows Machine Config Operator