What happened:
The kubelet cAdvisor metrics are missing the runtime values meaning we can't see the node usage.
What you expected to happen:
I'd expect to see the runtime values as part of the kubelet metrics.
How to reproduce it (as minimally and precisely as possible):
Run kubectl get --raw "/api/v1/nodes/${NODE_NAME}/proxy/stats/summary" | jq -r '.node.systemContainers[] | .name' and you'll see the following response.
kubelet
pods
Anything else we need to know?:
This appears to be broken because the --runtime-cgroups=/runtime.slice/containerd.service kubelet argument hasn't been set. I can confirm that if this argument has been set the outcome of the command above is a as follows.
stevehipwell
commented
4 months ago
What happened: The kubelet cAdvisor metrics are missing the runtime values meaning we can't see the node usage.
What you expected to happen: I'd expect to see the runtime values as part of the kubelet metrics.
How to reproduce it (as minimally and precisely as possible): Run
kubectl get --raw "/api/v1/nodes/${NODE_NAME}/proxy/stats/summary" | jq -r '.node.systemContainers[] | .name'and you'll see the following response.Anything else we need to know?: This appears to be broken because the
--runtime-cgroups=/runtime.slice/containerd.servicekubelet argument hasn't been set. I can confirm that if this argument has been set the outcome of the command above is a as follows.Environment: