Question: K8s components monitoring

[lukasmrtvy]

Hello, why did You disabled https://github.com/cablespaghetti/k3s-monitoring/blob/master/kube-prometheus-stack-values.yaml#L1-L6 ?

You can use:

  kubeEtcd:
    enabled: false
  kubeControllerManager:
    endpoints:
    - 88.XX.XX.XX
  kubeScheduler:
    endpoints:
    - 88.XX.XX.XX
  kubeProxy:
    endpoints:
    - 88.XX.XX.XX

, it will create Service/Endpoints in kube-system, what is problematic that ip in Endpoints does not allow FQDN, so You have to know IP address apriori. For example Service/Endpoints kubelet is created with that IP by operator automatically.

EDIT: seems these are scraped via apiserver and proxy ?

[cablespaghetti]

I had no idea this was possible. I'll try this when I have a chance! :)

[cablespaghetti]

Been trying to work this out. It does indeed seem like the metrics come through the apiserver and kube-proxy scrape jobs. However all the dashboards/rules that come with the chart have job="kube-scheduler" and job="kube-controller-manager" in them. I might fork the Helm chart and make it possible to change that for people like us on k3s.

[cablespaghetti]

I have found the answer! :)

prometheus-community/helm-charts#626