You can review the following release notes to learn about changes in the Windows Machine Config Operator (WMCO) version 10.18.2.
Issued: 11 March 2026
You can review the following release notes to learn about the bug fixes provided in this release of the Windows Machine Config Operator (WMCO).
The components of the WMCO 10.18.2 were released in RHBA-2026:4395.
Before this update, the hybridOverlay service was not using the trusted CA bundle when connecting to Kubernetes, because the --k8s-cacert option was missing from the service command. Because of this, users could encounter trust issues or failures when the hybridOverlay service attempted to communicate securely with Kubernetes clusters using custom or internal CAs. With this release, the hybridOverlay service command now includes the --k8s-cacert flag pointing to the trusted CA bundle. As a result, the hybridOverlay service uses the trusted CA bundle for secure communication, preventing trust issues and ensuring compatibility with the cluster. (OCPBUGS-65856)
Before this update, if you made a configuration change that required the WMCO to delete and re-create an internal config map, such as changing the proxy settings of the cluster, the WMCO pod panicked and entered a crash loop due to a nil pointer dereference panic. With this release, the error handling logic is reworked. As a result, the WMCO pod no longer crashes when an internal config map is recreated. (OCPBUGS-61743)
Before this update, Windows Server 2019 machines might not have a running SSH server because of network instability. As a result, the WMCO could not access some VMs to complete configuration. With this release, the WMCO makes multiple attempt to SSH into the VM. As such, SSH connectivity to VMs is restored, ensuring smooth configuration and management of nodes. (OCPBUGS-60774)