From b4cb812a1d216d5a0b8fe189879cd91a329cad8c Mon Sep 17 00:00:00 2001 From: Suhel Khan Date: Mon, 15 Feb 2021 11:14:18 +0530 Subject: [PATCH] Update horizontal-pod-autoscale.md With `v2beta2` controller can take replication decision on memory and custom metric utilisation as well. --- .../en/docs/tasks/run-application/horizontal-pod-autoscale.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md index 763d9ab996..ed99e9bd96 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -23,9 +23,7 @@ Pod Autoscaling does not apply to objects that can't be scaled, for example, Dae The Horizontal Pod Autoscaler is implemented as a Kubernetes API resource and a controller. The resource determines the behavior of the controller. -The controller periodically adjusts the number of replicas in a replication controller or deployment -to match the observed average CPU utilization to the target specified by user. - +The controller periodically adjusts the number of replicas in a replication controller or deployment to match the observed metrics such as average CPU utilisation, average memory utilisation or any other custom metric to the target specified by the user.