From db056570a9f589b2a4f2a56ff11064ae3d6688fd Mon Sep 17 00:00:00 2001 From: Shannon Kularathna Date: Sat, 5 Mar 2022 11:29:44 -0500 Subject: [PATCH] Remove 'Legacy Docker integration' from cAdvisor sentence Co-authored-by: Tim Bannister --- .../tasks/debug/debug-cluster/resource-usage-monitoring.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/debug/debug-cluster/resource-usage-monitoring.md b/content/en/docs/tasks/debug/debug-cluster/resource-usage-monitoring.md index b02d6ab31a..3c270b8122 100644 --- a/content/en/docs/tasks/debug/debug-cluster/resource-usage-monitoring.md +++ b/content/en/docs/tasks/debug/debug-cluster/resource-usage-monitoring.md @@ -41,8 +41,11 @@ memory usage. The kubelet acts as a bridge between the Kubernetes master and the nodes, managing the pods and containers running on a machine. The kubelet translates each pod into its constituent containers and fetches individual container usage statistics from the container runtime through the container -runtime interface. The kubelet fetches this information from the integrated -cAdvisor for the legacy Docker integration. It then exposes the aggregated pod +runtime interface. If you use a container runtime that uses Linux cgroups and +namespaces to implement containers, and the container runtime does not publish +usage statistics, then the kubelet can look up those statistics directly +(using code from [cAdvisor](https://github.com/google/cadvisor)). +No matter how those statistics arrive, the kubelet then exposes the aggregated pod resource usage statistics through the metrics-server Resource Metrics API. This API is served at `/metrics/resource/v1beta1` on the kubelet's authenticated and read-only ports.