From f6eafd9480c0a2119d31b8f18a213d98cd9487d5 Mon Sep 17 00:00:00 2001 From: Becca Bau Date: Tue, 18 Aug 2020 18:32:45 -0400 Subject: [PATCH] Update content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md Avoiding Latin phrasing Co-authored-by: Zach Corleissen --- .../debug-application-cluster/resource-metrics-pipeline.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md b/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md index eb2240793a..f5f2e78ba2 100644 --- a/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md +++ b/content/en/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md @@ -10,7 +10,7 @@ content_type: concept Resource usage metrics, such as container CPU and memory usage, are available in Kubernetes through the Metrics API. These metrics can be accessed either directly -by the user, i.e. by using the `kubectl top` command, or by a controller in the cluster, e.g. +by the user with the `kubectl top` command, or by a controller in the cluster, for example Horizontal Pod Autoscaler, to make decisions. @@ -65,4 +65,3 @@ Metrics Server collects metrics from the Summary API, exposed by Learn more about the metrics server in [the design doc](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/metrics-server.md). -