[Release-1.26] - In windows, kube-proxy does not log the error and calico logs are in the wrong path

[manuelbuil]

Backport fix for In windows, kube-proxy does not log the error and calico logs are in the wrong path

• In windows, kube-proxy does not log the error and calico logs are in the wrong path #5247

[mdrahman-suse]

Validated with version v1.26.13-rc2+rke2r1

Environment Details

Infrastructure

• Cloud
• Hosted

Node(s) CPU architecture, OS, and Version:

Ubuntu 22.04, Windows 2022

Cluster Configuration:

1 server, 1 agent (optional), 1 windows agent

Testing Steps

1. Install RKE2 and join linux (optional) and windows agent
2. Check the logs are present in Windows agent under C:\var\lib\rancher\rke2\agent\logs

Replication Results:

• rke2 version used for replication:

rke2.exe version v1.26.12+rke2r1 (10683d5a09610873f643ada416b97eb01859108d)
go version go1.20.12

> ls C:\var\lib\rancher\rke2\agent\logs


    Directory: C:\var\lib\rancher\rke2\agent\logs


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         1/22/2024  10:23 PM              0 kubelet.log

Validation Results:

• rke2 version used for validation:

rke2.exe version v1.26.13-rc2+rke2r1 (759709e78f0b5138a2d632aa5665d2b2c5dcdc10)
go version go1.20.13

> ls C:\var\lib\rancher\rke2\agent\logs


    Directory: C:\var\lib\rancher\rke2\agent\logs


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         1/22/2024  10:28 PM           3044 calico-node.log
-a----         1/22/2024  10:28 PM              0 felix.log
-a----         1/22/2024  10:28 PM              0 kube-proxy.log
-a----         1/22/2024  10:28 PM              0 kubelet.log