From 055796ea4a9e249caaf645995f541a227cb809ef Mon Sep 17 00:00:00 2001 From: Lauren Hughes Date: Thu, 23 Apr 2020 16:04:11 -0700 Subject: [PATCH] Fix broken link Structure of the repo changed and broke the link, see [Deployment](https://github.com/kubernetes-sigs/metrics-server/blob/master/README.md#deployment) section of the readme for more info --- .../debug-application-cluster/resource-metrics-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 072070ab66..925577d8b1 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 @@ -52,7 +52,7 @@ Memory is reported as the working set, in bytes, at the instant the metric was c [Metrics Server](https://github.com/kubernetes-incubator/metrics-server) is a cluster-wide aggregator of resource usage data. It is deployed by default in clusters created by `kube-up.sh` script as a Deployment object. If you use a different Kubernetes setup mechanism you can deploy it using the provided -[deployment yamls](https://github.com/kubernetes-incubator/metrics-server/tree/master/deploy). +[deployment component.yaml](https://github.com/kubernetes-sigs/metrics-server/releases) file. Metric server collects metrics from the Summary API, exposed by [Kubelet](/docs/admin/kubelet/) on each node.