monitoring: scrape kubelet/cAdvisor directly on :10250

The API server proxy path (nodes/proxy) returned 403. Kubelet certs are
verified against k3s-server-ca from the service account.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
un-oeil 2026-10-25 23:30:59 +01:00
parent 8983fe295c
commit 5c9d3910c5

View file

@ -102,12 +102,16 @@ spec:
role = "pod"
}
// kubelet and cAdvisor, through the API server proxy
// kubelet and cAdvisor, straight from each kubelet (:10250). The API
// server proxy path (nodes/proxy) answers 403 on this k3s. The
// kubelet serving certs are signed by k3s-server-ca (the same CA as
// the service account's ca.crt) and carry the node IP as a SAN.
discovery.relabel "kubelet" {
targets = discovery.kubernetes.nodes.targets
rule {
source_labels = ["__meta_kubernetes_node_address_InternalIP"]
target_label = "__address__"
replacement = "kubernetes.default.svc:443"
replacement = "$1:10250"
}
rule {
source_labels = ["__meta_kubernetes_node_name"]
@ -115,17 +119,15 @@ spec:
}
rule {
source_labels = ["__meta_kubernetes_node_name"]
target_label = "__metrics_path__"
replacement = "/api/v1/nodes/$1/proxy/metrics"
target_label = "instance"
}
}
discovery.relabel "cadvisor" {
targets = discovery.relabel.kubelet.output
rule {
source_labels = ["node"]
target_label = "__metrics_path__"
replacement = "/api/v1/nodes/$1/proxy/metrics/cadvisor"
replacement = "/metrics/cadvisor"
}
}