WMCO 10.18.1 release notes

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

@@ -7,43 +7,28 @@ include::_attributes/common-attributes.adoc[]
 toc::[]
 
 
-[id="wmco-10-18-0"]
-== Release notes for Red Hat Windows Machine Config Operator 10.18.0
+[id="wmco-10-18-1"]
+== Release notes for Red Hat Windows Machine Config Operator 10.18.1
 
 Issued: 19 March 2025
 
 This release of the Windows Machine Config Operator (WMCO) provides bug fixes for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 10.18.0 were released in link:https://access.redhat.com/errata/RHBA-2025:3040[RHBA-2025:3040].
 
-[id="wmco-10-18-0-new-features"]
+[id="wmco-10-18-1-new-features"]
 === New features and improvements
 
-[id="wmco-10-18-0-new-features-hpa"]
-==== Horizontal Pod autoscaling is available for Windows workloads
-You can now use a horizontal pod autoscaler (HPA) to scale your Windows pods based on CPU and/or memory resource metrics. For more information on using an HPA, see xref:../../nodes/pods/nodes-pods-autoscaling.adoc#nodes-pods-autoscaling[Automatically scaling pods with the horizontal pod autoscaler].
+[id="wmco-10-18-0-new-features-debuglogging"]
+==== WMCO kubelet configuration changes 
 
-[id="wmco-10-18-0-new-features-eus"]
-==== Control Plane Only updates are now available for Windows nodes
-You can now use *Control Plane Only* updates, previously known as *EUS-to-EUS* updates, to update your Windows nodes between {product-title} EUS versions. For more information, see xref:../../windows_containers/windows-node-upgrades.adoc#wmco-upgrades-eus_windows-node-upgrades[Windows Machine Config Operator Control Plane Only upgrade].
+With this release, the WMCO now sets the following values in the `KubeletConfig` custom resource (CR):
 
-[id="wmco-10-18-0-new-features-metrics"]
-==== WMCO metrics endpoint is now HTTPS
-The WMCO metrics endpoint is now exposed over HTTPS. Previously, WMCO pod metrics were available over HTTP. This change improves the security posture of the WMCO metrics endpoint.
-// https://issues.redhat.com/browse/WINC-1269
-// https://issues.redhat.com/browse/WINC-588
+* The `system-reserved` parameter is now set to 2GiB of memory for system processes, as recommended in the link:https://kubernetes.io/docs/concepts/configuration/windows-resource-management/#resource-reservation[Kubernetes documentation].
+* The `enforceNodeAllocatable` with  a default value of `none`. Previously, the value was set to `[]` to avoid a known issue. Both settings disable the enforcement of node allocatable resource limits.
+* The `evictionHard` parameters, `imagefs.available` and `nodefs.available` are now set to `15%` and `10%` respectively, as recommended in the link:https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals[Kubernetes documentation] 
 
-[id="wmco-10-18-0-new-features-debuglogging"]
-==== WMCO now defaults to info-level logging
-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. 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].
+The `KubeletConfig` object configures the kubelet service, which runs on each node in the cluster to ensure that containers in a pod are running.
 
-[id="wmco-10-18-0-new-features-kubernetes"]
-==== Kubernetes upgrade
-The WMCO now uses Kubernetes 1.31.
+// https://github.com/openshift/windows-machine-config-operator/pull/2709
 
-[id="wmco-10-18-0-bug-fixes"]
+[id="wmco-10-18-1-bug-fixes"]
 === Bug fixes
-* Previously, if you installed the WMCO into the the default `openshift-windows-machine-config-operator` namespace and removed the WMCO, subsequently installing the WMCO into a namespace other than the default would fail. This was because the role-based access control (RBAC) for the Windows Instance Config Daemon (WICD) was always associated with the default namespace. With this fix, when installing the WMCO to a non-default namespace, the RBAC for the WICD is configured correctly. (link:https://issues.redhat.com/browse/OCPBUGS-46473[*OCPBUGS-46473*])
-
-* Previously, the {product-title} documentation lacked information about WMCO support for the installer-provisioned infrastructure and the user-provisioned infrastructure installation methods. With this fix, the documentation now reports that the installer-provisioned infrastructure method is the preferred installation method and can be used with all platforms. The user-provisioned infrastructure method is limited to specific use cases. For more information, see xref:../../windows_containers/wmco_rn/windows-containers-release-notes-10-18-x-prereqs.adoc#wmco-prerequisites-supported-install-10.18.0_windows-containers-release-notes-10-18-x-prereqs[WMCO supported installation method]. (link:https://issues.redhat.com/browse/OCPBUGS-18898[*OCPBUGS-18898*])
-
-// Bug fixes listed in https://gitlab.cee.redhat.com/releng/advisories/-/blob/main/data/advisories/windows-machine-conf-tenant/2025/3040/advisory.yaml?ref_type=heads, as the advisory did not contain the list at the time these RN were created.
-// https://issues.redhat.com/browse/WINC-1149, no release note required. Documented via https://github.com/openshift/openshift-docs/pull/80320