History

Arvind Iyengar 18f0a74a13 make standardize		2022-01-06 11:08:03 -08:00
..
scripts	make standardize	2022-01-06 11:08:03 -08:00
templates	make standardize	2022-01-06 11:08:03 -08:00
.helmignore	make standardize	2022-01-06 11:08:03 -08:00
Chart.yaml	make standardize	2022-01-06 11:08:03 -08:00
README.md	make standardize	2022-01-06 11:08:03 -08:00
values.yaml	make standardize	2022-01-06 11:08:03 -08:00

README.md

rancher-windows-exporter

A Rancher chart based on the prometheus-community/windows-exporter project (previously called wmi-exporter) that sets up a DaemonSet of clients that can scrape windows-exporter metrics from Windows nodes on a Kubernetes cluster.

A Prometheus Operator ServiceMonitor CR and PrometheusRule CR are also created by this chart to collect metrics and add some recording rules to map windows_ series with their OS-agnostic counterparts.

Node Requirements

Since Windows does not support privileged pods, this chart expects a Named Pipe (\\.\pipe\rancher_wins) to exist on the Windows host that allows containers to communicate with the host. This is done by deploying a rancher/wins server on the host.

The image used by the chart, windows_exporter-package, is configured to create a wins client that communicates with the wins server, alongside a running copy of a particular version of windows-exporter. Through the wins client and wins server, the windows-exporter is able to communicate directly with the Windows host to collect metrics and expose them.

If the cluster you are installing this chart on is a custom cluster that was created via RKE1 with Windows Support enabled, your nodes should already have the wins server running; this should have been added as part of the bootstrapping process for adding the Windows node onto your RKE1 cluster.

Configuration

See rancher-monitoring for an example of how this chart can be used.