https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
K3s has all the same parts as any other Kubernetes distro, including the kubelet. They just all run in a single process.
What are you trying, and what problem did you run into?
l
Well, assuming kubelet even includes the metrics I care about, I'm trying to use grafana agent's 
discovery.kubelet
component (https://grafana.com/docs/agent/latest/flow/reference/components/discovery.kubelet/) to fetch them. But by default it expects them to be available on the pod at port 10250, and they aren't
Which I thought might be a side effect of kubelet being in the same process as everything else, but I could be totally off base there
Where can I find those metrics, if not there on port 10250?
(I'm happy with a RTFM, I just need a link to TFM in this case 😛 )
c
What do you mean by “on the pod”. The kubelet doesn’t run in a pod. the kubelet is what RUNS pods.
kubelet metrics are available on the node on that port
l
Yeah obviously I have no clue, I just ran that component and it complained that nothing was on that port, so at that point I wasn't sure what I was misunderstanding: grafana, k8s, or k3s 😛
Confirmed though, thank you, that's on the node indeed
4 Views
Open in Slack
PreviousNext
Powered by