From da139b36be8faf55f097f3037e5f51e18a03738e Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Thu, 10 Aug 2017 01:07:21 +0800 Subject: [PATCH] Update kubectl get scale's output (#4708) --- .../horizontal-pod-autoscale-walkthrough.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md index ac47ca09d4..b44baa485f 100644 --- a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md +++ b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md @@ -60,8 +60,8 @@ We may check the current status of autoscaler by running: ```shell $ kubectl get hpa -NAME REFERENCE TARGET CURRENT MINPODS MAXPODS AGE -php-apache Deployment/php-apache/scale 50% 0% 1 10 18s +NAME REFERENCE TARGET MINPODS MAXPODS REPLICAS AGE +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 $ kubectl get hpa -NAME REFERENCE TARGET CURRENT MINPODS MAXPODS AGE -php-apache Deployment/php-apache/scale 50% 305% 1 10 3m +NAME REFERENCE TARGET CURRENT MINPODS MAXPODS REPLICAS AGE +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 $ kubectl get hpa -NAME REFERENCE TARGET CURRENT MINPODS MAXPODS AGE -php-apache Deployment/php-apache/scale 50% 0% 1 10 11m +NAME REFERENCE TARGET MINPODS MAXPODS REPLICAS AGE +php-apache Deployment/php-apache/scale 0% / 50% 1 10 1 11m $ kubectl get deployment php-apache NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE