-
After reading https://docs.k3s.io/installation/registry-mirror
The docs state If all nodes are hosting, why are there only metrics for control-plane nodes with switch enabled? Checking a Control-Plane node:
Checking a Worker node:
It does look look like all hosts have ports opened. Is it just an issue with metrics not being exposed/collected on worker nodes? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
This would appear to be an issue with your scraper config. The Spegel metrics are mixed in with the rest of the metrics, which are exposed via all metrics endpoints due to how K3s runs all the Kubernetes components in a single process. Check the metrics available on the kubelet metrics port, you should find them in there. That's where I usually poll my metrics from, since all nodes have a kubelet - while only server nodes have the apiserver + apiserver metrics endpoint. See also: #9951 |
Beta Was this translation helpful? Give feedback.
-
Thank you... that was the hint I needed.
I did have a filter, adjusted and they show up now. |
Beta Was this translation helpful? Give feedback.
This would appear to be an issue with your scraper config. The Spegel metrics are mixed in with the rest of the metrics, which are exposed via all metrics endpoints due to how K3s runs all the Kubernetes components in a single process. Check the metrics available on the kubelet metrics port, you should find them in there. That's where I usually poll my metrics from, since all nodes have a kubelet - while only server nodes have the apiserver + apiserver metrics endpoint.
See also: #9951