[release-1.10] Update autoscaling-metrics.md for modifications (#5585)

* Update autoscaling-metrics.md for modifications

* Update autoscaling-metrics.md

---------

Co-authored-by: achiverram28 <97288756+achiverram28@users.noreply.github.com>
This commit is contained in:
Knative Prow Robot 2023-05-31 16:25:36 +01:00 committed by GitHub
parent f6814d842d
commit ec8b851ee0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions

View File

@ -15,11 +15,11 @@ The possible metric types that can be configured per revision depend on the type
For more information about KPA and HPA, see the documentation on [Supported Autoscaler types](autoscaler-types.md).
* **Per-revision annotation key:** `autoscaling.knative.dev/metric`
* **Possible values:** `"concurrency"`, `"rps"`, `"cpu"`, `"memory"` or any custom metric name, depending on your Autoscaler type. The `"cpu"`, `"memory"`, and `"custom"` metrics are only supported on revisions that use the HPA class.
* **Possible values:** `"concurrency"`, `"rps"`, `"cpu"`, `"memory"` or any custom metric name, depending on your Autoscaler type. The `"cpu"`, `"memory"`, and custom metrics are supported on revisions that use the HPA class.
* **Default:** `"concurrency"`
=== "Per-revision concurrency configuration"
=== "Concurrency"
```yaml
apiVersion: serving.knative.dev/v1
@ -34,7 +34,7 @@ For more information about KPA and HPA, see the documentation on [Supported Auto
autoscaling.knative.dev/metric: "concurrency"
```
=== "Per-revision rps configuration"
=== "Requests per second"
```yaml
apiVersion: serving.knative.dev/v1
@ -49,7 +49,7 @@ For more information about KPA and HPA, see the documentation on [Supported Auto
autoscaling.knative.dev/metric: "rps"
```
=== "Per-revision cpu configuration"
=== "CPU"
```yaml
apiVersion: serving.knative.dev/v1
@ -65,7 +65,7 @@ For more information about KPA and HPA, see the documentation on [Supported Auto
autoscaling.knative.dev/metric: "cpu"
```
=== "Per-revision memory configuration"
=== "Memory"
```yaml
apiVersion: serving.knative.dev/v1
@ -81,7 +81,7 @@ For more information about KPA and HPA, see the documentation on [Supported Auto
autoscaling.knative.dev/metric: "memory"
```
=== "Per-revision custom metric configuration"
=== "Custom metric"
You can create an HPA to scale the revision by a metric that you specify.
The HPA will be configured to use the **average value** of your metric over all the Pods of the revision.