1. Proposed title of this feature request

Request for Log Rotation Support for Kubelet, Containerd, and Kube-Proxy Logs on Windows Nodes Managed by WMCO

2. What is the nature and description of the request?

Description:

Currently, Windows worker nodes managed by the Windows Machine Config Operator (WMCO) accumulate large log files under C:\var\log over time. Key components like:

• kubelet.log

• containerd.log

• kube-proxy.log

generate logs continuously, but there is no log rotation or purging mechanism available on Windows as there is on Linux (via logrotate, journald, etc.). As a result, disk usage can grow uncontrollably and impact node stability.

Problem Statement:

There is no supported or automated way to rotate or purge logs generated by core Kubernetes components on Windows nodes in OpenShift. Manually addressing this with scheduled tasks or external scripts introduces operational risk and inconsistency.

Affected Components:

• WMCO (Windows Machine Config Operator)

• Windows Worker Nodes in OpenShift 4.x

Expected Enhancement:

Add built-in log rotation or purging support for the following logs in WMCO-managed Windows nodes:

• C:\var\log\kubelet.log

• C:\var\log\containerd.log

• C:\var\log\kube-proxy.log

This could be implemented via:

• Scheduled Task creation during WMCO bootstrap

• PowerShell script integration with configurable retention/size limit

• Support for rotation settings via WMCO ConfigMap or annotation

3. Why does the customer need this? (List the business requirements here)

Value to Customer:

• Prevent disk exhaustion on Windows nodes

• Reduce manual operational overhead and risk

• Bring feature parity with Linux nodes (which use logrotate/journald)

• Improve cluster reliability and node uptime

4. List any affected packages or components.

WMCO