v2, k3s: kubeControllerManager, kubeScheduler & kubeProxy metrics

[pschiffe]

Hello, was anyone able to collect metrics of kubeControllerManager, kubeScheduler & kubeProxy on k3s? I don't think there are pods in the kube-system with component=kube-controller-manager, etc.

Based on this thread, k3s exposes metrics for kubeControllerManager, kubeScheduler & kubeProxy only on the host, as far as I understand. When looking at the rancher-monitoring chart, it seem like they are using rancher-pushprox for accessing metrics from the host.

Is this something this helm chart would support as well? Do you have some tips how to best implement this in the current version of v2?

Thanks.