diff --git a/examples/cassandra/README.md b/examples/cassandra/README.md index 5d9fa2d43be..7523a5e372e 100644 --- a/examples/cassandra/README.md +++ b/examples/cassandra/README.md @@ -91,7 +91,7 @@ After a few moments, you should be able to see the pod running, plus its single ```sh $ kubectl get pods cassandra -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE cassandra 1/1 Running 0 55s ``` @@ -192,7 +192,7 @@ Now if you list the pods in your cluster, and filter to the label ```name=cassan ```sh $ kubectl get pods -l="name=cassandra" -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE cassandra 1/1 Running 0 3m cassandra-af6h5 1/1 Running 0 28s ``` diff --git a/examples/guestbook-go/README.md b/examples/guestbook-go/README.md index 5de1bdd748c..6ee6ce15f6d 100644 --- a/examples/guestbook-go/README.md +++ b/examples/guestbook-go/README.md @@ -43,7 +43,7 @@ Use the `examples/guestbook-go/redis-master-controller.json` file to create a [r 3. To verify that the redis-master pod is running, list all the pods in cluster with the `kubectl get pods` command: ```shell $ kubectl get pods - NAME READY REASON RESTARTS AGE + NAME READY STATUS RESTARTS AGE redis-master-xx4uv 1/1 Running 0 1m ... ``` @@ -108,7 +108,7 @@ The Redis master we created earlier is a single pod (REPLICAS = 1), while the Re 2. To verify that the Redis master and slaves pods are running, run the `kubectl get pods` command: ```shell $ kubectl get pods - NAME READY REASON RESTARTS AGE + NAME READY STATUS RESTARTS AGE redis-master-xx4uv 1/1 Running 0 18m redis-slave-b6wj4 1/1 Running 0 1m redis-slave-iai40 1/1 Running 0 1m @@ -161,7 +161,7 @@ This is a simple Go `net/http` ([negroni](https://github.com/codegangsta/negroni 3. To verify that the guestbook pods are running (it might take up to thirty seconds to create the pods), list all the pods in cluster with the `kubectl get pods` command: ```shell $ kubectl get pods - NAME READY REASON RESTARTS AGE + NAME READY STATUS RESTARTS AGE guestbook-3crgn 1/1 Running 0 2m guestbook-gv7i6 1/1 Running 0 2m guestbook-x405a 1/1 Running 0 2m diff --git a/examples/guestbook/README.md b/examples/guestbook/README.md index ed5dcc34784..dbd8ba29b98 100644 --- a/examples/guestbook/README.md +++ b/examples/guestbook/README.md @@ -94,7 +94,7 @@ You'll see all pods in the cluster, including the redis master pod, and the stat The name of the redis master will look similar to that in the following list: ```shell -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE ... redis-master-dz33o 1/1 Running 0 2h ``` @@ -267,7 +267,7 @@ Once the replication controller is up, you can list the pods in the cluster, to ```shell $ kubectl get pods -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE ... redis-master-dz33o 1/1 Running 0 2h redis-slave-35mer 1/1 Running 0 2h @@ -363,7 +363,7 @@ Once it's up (again, it may take up to thirty seconds to create the pods) you ca ```shell $ kubectl get pods -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE ... frontend-4o11g 1/1 Running 0 2h frontend-u9aq6 1/1 Running 0 2h diff --git a/examples/liveness/README.md b/examples/liveness/README.md index 1b37875d690..eff75d37556 100644 --- a/examples/liveness/README.md +++ b/examples/liveness/README.md @@ -43,7 +43,7 @@ To show the health check is actually working, first create the pods: Check the status of the pods once they are created: ``` # kubectl get pods -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE [...] liveness-exec 1/1 Running 0 13s liveness-http 1/1 Running 0 13s @@ -52,7 +52,7 @@ Check the status half a minute later, you will see the container restart count b ``` # kubectl get pods mwielgus@mwielgusd:~/test/k2/kubernetes/examples/liveness$ kubectl get pods -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE [...] liveness-exec 1/1 Running 1 36s liveness-http 1/1 Running 1 36s diff --git a/examples/logging-demo/README.md b/examples/logging-demo/README.md index 65c3dd85c8a..70262681031 100644 --- a/examples/logging-demo/README.md +++ b/examples/logging-demo/README.md @@ -50,7 +50,7 @@ You can report the running pods, [replication controllers](../../docs/replicatio ``` $ make get ../../cluster/kubectl.sh get pods -NAME READY REASON RESTARTS AGE +NAME READY STATUS RESTARTS AGE elasticsearch-logging-v1-gzknt 1/1 Running 0 11m elasticsearch-logging-v1-swgzc 1/1 Running 0 11m fluentd-elasticsearch-kubernetes-minion-1rtv 1/1 Running 0 11m