From 9e74703ad193547074312d41ea797fe90ebe4c7e Mon Sep 17 00:00:00 2001 From: Fabian Deutsch Date: Fri, 14 Jul 2017 12:35:39 +0200 Subject: [PATCH] docs: Fix link in horizontal-pod-autoscale to #support-for-custom-metrics --- docs/tasks/run-application/horizontal-pod-autoscale.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/run-application/horizontal-pod-autoscale.md b/docs/tasks/run-application/horizontal-pod-autoscale.md index ee504883a3..c900799f46 100644 --- a/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -59,7 +59,7 @@ When using direct Heapster access, the HorizontalPodAutoscaler queries Heapster through the API server's service proxy subresource. Heapster needs to be deployed on the cluster and running in the kube-system namespace. -See [Support for custom metrics](#prerequisites) for more details on REST client access. +See [Support for custom metrics](#support-for-custom-metrics) for more details on REST client access. The autoscaler accesses corresponding replication controller, deployment or replica set by scale sub-resource. Scale is an interface that allows you to dynamically set the number of replicas and examine each of their current states.