Merge pull request #162 from lachie83/bugfix-update-readme

Fix label to use component rather than app in README
This commit is contained in:
Adnan Abdulhussein
2016-11-01 09:58:35 -07:00
committed by GitHub
3 changed files with 9 additions and 9 deletions
+3 -3
View File
@@ -155,7 +155,7 @@ Waiting for consul-2.consul to come up
The consul cluster can be scaled up by running ``kubectl patch`` or ``kubectl edit``. For example,
```
kubectl get pods -l "app=consul" --namespace=consul
kubectl get pods -l "component=${RELEASE-NAME}-consul" --namespace=consul
NAME READY STATUS RESTARTS AGE
consul-0 1/1 Running 1 4h
consul-1 1/1 Running 0 4h
@@ -164,7 +164,7 @@ consul-2 1/1 Running 0 4h
$ kubectl patch petset/consul -p '{"spec":{"replicas": 5}}'
"consul" patched
kubectl get pods -l "app=consul" --namespace=consul
kubectl get pods -l "component=${RELEASE-NAME}-consul" --namespace=consul
NAME READY STATUS RESTARTS AGE
consul-0 1/1 Running 1 4h
consul-1 1/1 Running 0 4h
@@ -209,7 +209,7 @@ Scale down
```
kubectl patch petset/consul -p '{"spec":{"replicas": 3}}' --namespace=consul
"consul" patched
lachlanevenson@faux$ kubectl get pods -l "app=consul" --namespace=consul
lachlanevenson@faux$ kubectl get pods -l "component=${RELEASE-NAME}-consul" --namespace=consul
NAME READY STATUS RESTARTS AGE
consul-0 1/1 Running 1 4h
consul-1 1/1 Running 0 4h
+5 -5
View File
@@ -92,7 +92,7 @@ $ kill -9 ETCD_1_PID
```
```shell
$ kubectl get pods -l "app=etcd"
$ kubectl get pods -l "component=${RELEASE-NAME}-etcd"
NAME READY STATUS RESTARTS AGE
etcd-0 1/1 Running 0 54s
etcd-2 1/1 Running 0 51s
@@ -101,7 +101,7 @@ etcd-2 1/1 Running 0 51s
After a while:
```shell
$ kubectl get pods -l "app=etcd"
$ kubectl get pods -l "component=${RELEASE-NAME}-etcd"
NAME READY STATUS RESTARTS AGE
etcd-0 1/1 Running 0 1m
etcd-1 1/1 Running 0 20s
@@ -131,7 +131,7 @@ This is for reference. Scaling should be managed by `helm upgrade`
The etcd cluster can be scale up by running ``kubectl patch`` or ``kubectl edit``. For instance,
```sh
$ kubectl get pods -l "app=etcd"
$ kubectl get pods -l "component=${RELEASE-NAME}-etcd"
NAME READY STATUS RESTARTS AGE
etcd-0 1/1 Running 0 7m
etcd-1 1/1 Running 0 7m
@@ -140,7 +140,7 @@ etcd-2 1/1 Running 0 6m
$ kubectl patch petset/etcd -p '{"spec":{"replicas": 5}}'
"etcd" patched
$ kubectl get pods -l "app=etcd"
$ kubectl get pods -l "component=${RELEASE-NAME}-etcd"
NAME READY STATUS RESTARTS AGE
etcd-0 1/1 Running 0 8m
etcd-1 1/1 Running 0 8m
@@ -155,7 +155,7 @@ Scaling-down is similar. For instance, changing the number of pets to ``4``:
$ kubectl edit petset/etcd
petset "etcd" edited
$ kubectl get pods -l "app=etcd"
$ kubectl get pods -l "component=${RELEASE-NAME}-etcd"
NAME READY STATUS RESTARTS AGE
etcd-0 1/1 Running 0 8m
etcd-1 1/1 Running 0 8m
+1 -1
View File
@@ -77,7 +77,7 @@ zoo-2 Mode: follower
Delete pets and wait for the petset controller to bring the back up:
```console
$ kubectl delete po -l app=zk
$ kubectl delete po -l component=${RELEASE-NAME}-zk
$ kubectl get po --watch-only
NAME READY STATUS RESTARTS AGE
zoo-0 0/1 Init:0/2 0 16s