summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2018-12-14 09:03:45 -0800
committerGitHub <noreply@github.com>2018-12-14 09:03:45 -0800
commit95bd29c0c6fcbb0d97ead0bdacc55811932a91a6 (patch)
tree890655ecb1313cb7c65c324c2fd23ec02f308841
parentd91b5a0ccfedfe3e8317067051507da2fed41fdf (diff)
parenta9175e178579ba69309213ab754448df5c3e80e7 (diff)
Merge pull request #3031 from sunnykrGupta/patch-1
HPA v2 API extension proposal | Dead link replaced
-rw-r--r--contributors/design-proposals/instrumentation/external-metrics-api.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/instrumentation/external-metrics-api.md b/contributors/design-proposals/instrumentation/external-metrics-api.md
index 3467f6aa..2b99ef12 100644
--- a/contributors/design-proposals/instrumentation/external-metrics-api.md
+++ b/contributors/design-proposals/instrumentation/external-metrics-api.md
@@ -2,7 +2,7 @@
# Overview
-[HPA v2 API extension proposal](https://github.com/kubernetes/community/blob/hpa_external/contributors/design-proposals/autoscaling/hpa-external-metrics.md) introduces new External metric type for autoscaling based on metrics coming from outside of Kubernetes cluster. This document proposes a new External Metrics API that will be used by HPA controller to get those metrics.
+[HPA v2 API extension proposal](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/autoscaling/hpa-external-metrics.md) introduces new External metric type for autoscaling based on metrics coming from outside of Kubernetes cluster. This document proposes a new External Metrics API that will be used by HPA controller to get those metrics.
This API performs a similar role to and is based on existing [Custom Metrics API](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/custom-metrics-api.md). Unless explicitly specified otherwise all sections related to semantics, implementation and design decisions in [Custom Metrics API design](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/custom-metrics-api.md) apply to External Metrics API as well. It is generally expected that a Custom Metrics Adapter will provide both Custom Metrics API and External Metrics API, however, this is not a requirement and both APIs can be implemented and used separately.