REASON to STATUS

This commit is contained in:
Chao Xu 2015-07-08 11:20:49 -07:00
parent 3cc13260ba
commit 1cca74c20d
3 changed files with 5 additions and 5 deletions

View File

@ -41,7 +41,7 @@ viewer should be running soon after the cluster comes to life.
```
$ kubectl get pods
NAME READY REASON RESTARTS AGE
NAME READY STATUS RESTARTS AGE
elasticsearch-logging-v1-78nog 1/1 Running 0 2h
elasticsearch-logging-v1-nj2nb 1/1 Running 0 2h
fluentd-elasticsearch-kubernetes-minion-5oq0 1/1 Running 0 2h

View File

@ -6,7 +6,7 @@ Cluster level logging for Kubernetes allows us to collect logs which persist bey
```
$ kubectl get pods
NAME READY REASON RESTARTS AGE
NAME READY STATUS RESTARTS AGE
fluentd-cloud-logging-kubernetes-minion-0f64 1/1 Running 0 32m
fluentd-cloud-logging-kubernetes-minion-27gf 1/1 Running 0 32m
fluentd-cloud-logging-kubernetes-minion-pk22 1/1 Running 0 31m
@ -45,7 +45,7 @@ This pod specification has one container which runs a bash script when the conta
We can observe the running pod:
```
$ kubectl get pods
NAME READY REASON RESTARTS AGE
NAME READY STATUS RESTARTS AGE
counter 1/1 Running 0 5m
fluentd-cloud-logging-kubernetes-minion-0f64 1/1 Running 0 55m
fluentd-cloud-logging-kubernetes-minion-27gf 1/1 Running 0 55m

View File

@ -137,7 +137,7 @@ Interact with the kubernetes-mesos framework via `kubectl`:
```bash
$ kubectl get pods
NAME READY REASON RESTARTS AGE
NAME READY STATUS RESTARTS AGE
```
```bash
@ -183,7 +183,7 @@ We can use the `kubectl` interface to monitor the status of our pod:
```bash
$ kubectl get pods
NAME READY REASON RESTARTS AGE
NAME READY STATUS RESTARTS AGE
nginx 1/1 Running 0 14s
```