kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

change kubectl get deployment output (#17351)

pull/17357/head
Luzhenxing 2019-11-02 12:31:40 +08:00 committed by Kubernetes Prow Robot
parent 4c48c963a0
commit 3aab039ac4
6 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/reference/kubectl/docker-cli-to-kubectl.md
View File

@ -257,8 +257,8 @@ kubectl:
kubectl get deployment nginx-app
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
nginx-app 1 1 1 1 2m
NAME READY UP-TO-DATE AVAILABLE AGE
nginx-app 1/1 1 1 2m
```
```shell

4
content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
View File

@ -49,8 +49,8 @@ for database debugging.
The output displays that the deployment was created:
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
redis-master 1 1 1 1 55s
NAME READY UP-TO-DATE AVAILABLE AGE
redis-master 1/1 1 1 55s
View the replicaset status using:

8
content/en/docs/tasks/administer-cluster/namespaces-walkthrough.md
View File

@ -235,8 +235,8 @@ If you want to obtain the old behavior, use `--generator=run/v1` to create repli
kubectl get deployment
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
snowflake 2 2 2 2 2m
NAME READY UP-TO-DATE AVAILABLE AGE
snowflake 2/2 2 2 2m
```
```shell
@ -271,8 +271,8 @@ kubectl run cattle --image=k8s.gcr.io/serve_hostname --replicas=5
kubectl get deployment
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
cattle 5 5 5 5 10s
NAME READY UP-TO-DATE AVAILABLE AGE
cattle 5/5 5 5 10s
```
```shell

8
content/en/docs/tasks/administer-cluster/namespaces.md
View File

@ -268,8 +268,8 @@ If you want to obtain the old behavior, use `--generator=run/v1` to create repli
kubectl get deployment
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
snowflake 2 2 2 2 2m
NAME READY UP-TO-DATE AVAILABLE AGE
snowflake 2/2 2 2 2m
```
```shell
kubectl get pods -l run=snowflake
@ -303,8 +303,8 @@ kubectl run cattle --image=k8s.gcr.io/serve_hostname --replicas=5
kubectl get deployment
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
cattle 5 5 5 5 10s
NAME READY UP-TO-DATE AVAILABLE AGE
cattle 5/5 5 5 10s
```
```shell

8
content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
View File

@ -135,8 +135,8 @@ As a result, the deployment was resized to 7 replicas:
kubectl get deployment php-apache
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
php-apache 7 7 7 7 19m
NAME READY UP-TO-DATE AVAILABLE AGE
php-apache 7/7 7 7 19m
```
{{< note >}}
@ -166,8 +166,8 @@ php-apache Deployment/php-apache/scale 0% / 50% 1 10 1
kubectl get deployment php-apache
```
```
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
php-apache 1 1 1 1 27m
NAME READY UP-TO-DATE AVAILABLE AGE
php-apache 1/1 1 1 27m
```
Here CPU utilization dropped to 0, and so HPA autoscaled the number of replicas back down to 1.

4
content/en/docs/tutorials/hello-minikube.md
View File

@ -90,8 +90,8 @@ Pod runs a Container based on the provided Docker image.
Output:
```shell
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
hello-node 1 1 1 1 1m
NAME READY UP-TO-DATE AVAILABLE AGE
hello-node 1/1 1 1 1m
```
3. View the Pod: