whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove 'Legacy Docker integration' from cAdvisor sentence

Browse Source 
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Shannon Kularathna
2022-03-05 11:29:44 -05:00
parent 6f0ebe94e2
commit db056570a9
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/debug/debug-cluster/resource-usage-monitoring.md
+5 -2
View File
@@ -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 the nodes, managing the pods and containers running on a machine. The kubelet
translates each pod into its constituent containers and fetches individual translates each pod into its constituent containers and fetches individual
container usage statistics from the container runtime through the container container usage statistics from the container runtime through the container
runtime interface. The kubelet fetches this information from the integrated runtime interface. If you use a container runtime that uses Linux cgroups and
cAdvisor for the legacy Docker integration. It then exposes the aggregated pod 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. resource usage statistics through the metrics-server Resource Metrics API.
This API is served at `/metrics/resource/v1beta1` on the kubelet's authenticated and This API is served at `/metrics/resource/v1beta1` on the kubelet's authenticated and
read-only ports. read-only ports.