Update kubectl get scale's output (#4708)
This commit is contained in:
committed by
Andrew Chen
parent
eceb421911
commit
da139b36be
@@ -60,8 +60,8 @@ We may check the current status of autoscaler by running:
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
$ kubectl get hpa
|
$ kubectl get hpa
|
||||||
NAME REFERENCE TARGET CURRENT MINPODS MAXPODS AGE
|
NAME REFERENCE TARGET MINPODS MAXPODS REPLICAS AGE
|
||||||
php-apache Deployment/php-apache/scale 50% 0% 1 10 18s
|
php-apache Deployment/php-apache/scale 0% / 50% 1 10 1 18s
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
@@ -85,8 +85,8 @@ Within a minute or so, we should see the higher CPU load by executing:
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
$ kubectl get hpa
|
$ kubectl get hpa
|
||||||
NAME REFERENCE TARGET CURRENT MINPODS MAXPODS AGE
|
NAME REFERENCE TARGET CURRENT MINPODS MAXPODS REPLICAS AGE
|
||||||
php-apache Deployment/php-apache/scale 50% 305% 1 10 3m
|
php-apache Deployment/php-apache/scale 305% / 50% 305% 1 10 1 3m
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
@@ -114,8 +114,8 @@ Then we will verify the result state (after a minute or so):
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
$ kubectl get hpa
|
$ kubectl get hpa
|
||||||
NAME REFERENCE TARGET CURRENT MINPODS MAXPODS AGE
|
NAME REFERENCE TARGET MINPODS MAXPODS REPLICAS AGE
|
||||||
php-apache Deployment/php-apache/scale 50% 0% 1 10 11m
|
php-apache Deployment/php-apache/scale 0% / 50% 1 10 1 11m
|
||||||
|
|
||||||
$ kubectl get deployment php-apache
|
$ kubectl get deployment php-apache
|
||||||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||||||
|
|||||||
Reference in New Issue
Block a user