From f983ecefa5e6887e9abb45bd89fddea2dcf00e53 Mon Sep 17 00:00:00 2001 From: zoues Date: Mon, 31 Jul 2017 15:56:19 +0800 Subject: [PATCH] Update hpa-v2.md --- contributors/design-proposals/hpa-v2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/hpa-v2.md b/contributors/design-proposals/hpa-v2.md index 55c990035..9f814ef59 100644 --- a/contributors/design-proposals/hpa-v2.md +++ b/contributors/design-proposals/hpa-v2.md @@ -281,7 +281,7 @@ Mechanical Concerns The HPA will derive metrics from two sources: resource metrics (i.e. CPU request percentage) will come from the [master metrics API](resource-metrics-api.md), while other metrics will -come from the [custom metrics API](custom-metrics-api.md)(currently proposed as #34586), which is +come from the [custom metrics API](custom-metrics-api.md), which is an adapter API which sources metrics directly from the monitoring pipeline.