diff options
| -rw-r--r-- | contributors/design-proposals/instrumentation/external-metrics-api.md | 2 |
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. |