windows node exporter fails

[ealasgarov]

@aiyengar2 - I guess it was you who added check-wins-version container back in the day: https://github.com/rancher/rancher/issues/31842

Rancher Server Setup

• Rancher version: 2.6.4

Information about the Cluster

• Kubernetes version: 1.23.8
• Cluster Type (Local/Downstream): AKS (both linux and windows node pools)

Describe the bug

I have installed Monitoring chart (100.1.3+up19.0.3) from rancher marketplace. Everything is up and running as expected except for windows-node-exporter daemonSet.

Pod has 3 containers in it: "check-wins-version" (init container), "exporter-node-proxy" & "exporter-node", image used: rancher/windows_exporter-package:v0.0.3

I can see, pod correctly landed on my windows node. In AKS my node is: AKSWindows-2019-containerd-17763.3287.220810.

Init container continuously fails (I cannot see the exact reason, not indicated anywhere), thus other 2 container cannot be starter either. If I remove the init container altogether, then both other containers are starting but then failing with:

INFO[2022-10-26T14:12:49Z] Connecting to proxy url="ws://rancher_wins_proxy"
--
Wed, Oct 26 2022 4:12:49 pm | ERRO[2022-10-26T14:12:49Z] Failed to connect to proxy. Empty dialer response error="open \\\\.\\pipe\\rancher_wins_proxy: The system cannot find the file specified."
Wed, Oct 26 2022 4:12:49 pm | FATA[2022-10-26T14:12:49Z] open \\.\pipe\rancher_wins_proxy: The system cannot find the file specified.

To Reproduce

Install the monitoring chart 100.1.3+up19.0.3 on cluster which has also windows nodes.

Result

Prometheus and other packages installed and up and running, except for windows node exporter DaemonSet.

Expected Result

Prometheus and other packages installed and up and running, including windows node exporter.