From 79d1dc5af02d06d0e30124870f0d75d6cccaea24 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Tue, 22 Oct 2019 16:01:07 -0700 Subject: [PATCH] Use cpu metric for CPU-based autoscaling sample Using `autoscaling.knative.dev/metric: concurrency` made no sense to me so I'm doing a quick PR. An example of this can be found at https://medium.com/@mchmarny_google/https-medium-com-p-knative-autoscaling-love-story-e32a27b7855 but let's not try to send people to external links to find how to do this. --- docs/serving/configuring-the-autoscaler.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/serving/configuring-the-autoscaler.md b/docs/serving/configuring-the-autoscaler.md index 3d43e8b00aa..be4e9400b78 100644 --- a/docs/serving/configuring-the-autoscaler.md +++ b/docs/serving/configuring-the-autoscaler.md @@ -180,10 +180,12 @@ spec: template: metadata: annotations: - autoscaling.knative.dev/metric: concurrency + autoscaling.knative.dev/metric: cpu + autoscaling.knative.dev/target: 70 autoscaling.knative.dev/class: hpa.autoscaling.knative.dev ``` + ## Additional resources - [Go autoscaling sample](https://knative.dev/docs/serving/samples/autoscale-go/index.html)