Closed nnlkcncff closed 1 year ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Page related to issue: https://kubernetes.io/docs/reference/instrumentation/cri-pod-container-metrics/ /language en
/sig node
I'm wondering if we really need to add documentations for the cAdvisor metrics. They are to be replaced by a kube-native mechanism. The substitution is still on-going. I'm not confident that someone will come up with a reference for this. This issue is gonna die away eventually. Feel free to reopen it if there are some heroes to step up for this challenge. /close
@tengqm: Closing this issue.
The sentense is confusing because it lacks detail. Two problems: 1) One cannot understand where this metrics are. Acording to the PodAndContainerStatsFromCRI feature gate the location is in the kubelet API at
/metrics/cadvisor
. 2) There wasn't any information on Concepts and Reference chapters before, but according to Node metrics data subchapter it states that cAdvisor is embedded in the kubelet.Also it would also be useful to add a link to cAdvisor metrics to clarify exactly what metrics are meant.
Please, consider adding this information to the page.
P.S. It’s also interesting where one can find a description of the metrics located in
/metrics
for kubelet, kube-proxy, kube-scheduler and kube-controller-manager, something like here or here.