diff --git a/modules/nodes-pods-autoscaling-creating-cpu.adoc b/modules/nodes-pods-autoscaling-creating-cpu.adoc index 43576dd720..fc63adf2e0 100644 --- a/modules/nodes-pods-autoscaling-creating-cpu.adoc +++ b/modules/nodes-pods-autoscaling-creating-cpu.adoc @@ -106,7 +106,7 @@ spec: name: cpu <9> target: type: Utilization <10> - averageValue: 500Mi <11> + averageValue: 500m <11> ---- <1> Use the `autoscaling/v2beta2` API. <2> Specify a name for this horizontal pod autoscaler object. @@ -131,10 +131,12 @@ $ oc create -f .yaml . Verify that the horizontal pod autoscaler was created: + ---- -$ oc get hpa hpa-resource-metrics-memory +$ oc get hpa cpu-autoscale + +NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE +cpu-autoscale ReplicationController/example 173m/500m 1 10 1 20m + -NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE -oc get hpa hpa-resource-metrics-memory ReplicationController/example 2441216/500Mi 1 10 1 20m ---- For example, the following command creates a horizontal pod autoscaler that maintains between 3 and 7 replicas of the Pods that are controlled by the `image-registry` DeploymentConfig in order to maintain an average CPU utilization of 75% across all Pods. diff --git a/modules/nodes-pods-autoscaling-creating-memory.adoc b/modules/nodes-pods-autoscaling-creating-memory.adoc index 66d672ceb3..67f8def989 100644 --- a/modules/nodes-pods-autoscaling-creating-memory.adoc +++ b/modules/nodes-pods-autoscaling-creating-memory.adoc @@ -168,8 +168,8 @@ horizontalpodautoscaler.autoscaling/hpa-resource-metrics-memory created ---- $ oc get hpa hpa-resource-metrics-memory -NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE -oc get hpa hpa-resource-metrics-memory ReplicationController/example 2441216/500Mi 1 10 1 20m +NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE +hpa-resource-metrics-memory ReplicationController/example 2441216/500Mi 1 10 1 20m ---- + ----