whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #878 from foxish/petset-docs

Browse Source 
Reviewed examples and petset docs, minor errors fixed.
This commit is contained in:
Prashanth B
2016-07-20 11:07:33 -07:00
committed by GitHub
parent 4fdf73c65f 00ca10945d
commit 327d1d3cc0
2 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/petset.md
+1 -1
View File
@@ -161,7 +161,7 @@ web-1
And the hostname is linked to the in-cluster DNS address: And the hostname is linked to the in-cluster DNS address:
```shell ```shell
$ kubectl run -it --image busybox dns-test --restart=Never /bin/sh $ kubectl run -i --tty --image busybox dns-test --restart=Never /bin/sh
dns-test # nslookup web-0.nginx dns-test # nslookup web-0.nginx
Server: 10.0.0.10 Server: 10.0.0.10
Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local
docs/user-guide/petset/bootstrapping/index.md
+12 -3
View File
@@ -32,7 +32,7 @@ Since Pet Set already gives each Pet a consistent identity, all we need is a way
Download [this](petset_vm.yaml) petset into a file called petset_vm.yaml, and create it: Download [this](petset_vm.yaml) petset into a file called petset_vm.yaml, and create it:
```shell ```shell
$ kubectl create -f ./petset_vm.yaml $ kubectl create -f petset_vm.yaml
service "ub" created service "ub" created
petset "vm" created petset "vm" created
``` ```
@@ -49,7 +49,7 @@ vm-1 1/1 Running 0 2m
We can exec into one and install nginx We can exec into one and install nginx
```shell ```shell
$ kubectl exec vm-0 /bin/sh $ kubectl exec -it vm-0 /bin/sh
vm-0 # apt-get update vm-0 # apt-get update
... ...
vm-0 # apt-get install nginx -y vm-0 # apt-get install nginx -y
@@ -79,6 +79,9 @@ And access it from anywhere in the cluster (and because this is an example that
```shell ```shell
$ kubectl exec -it vm-1 /bin/sh $ kubectl exec -it vm-1 /bin/sh
vm-1 # apt-get update
...
vm-1 # apt-get install netcat -y
vm-1 # printf "GET / HTTP/1.0\r\n\r\n" | netcat vm-0.ub 80 vm-1 # printf "GET / HTTP/1.0\r\n\r\n" | netcat vm-0.ub 80
``` ```
@@ -139,7 +142,10 @@ The role of the peer finder:
You can invoke the peer finder inside the Pets we created in the last example: You can invoke the peer finder inside the Pets we created in the last example:
```shell ```shell
$ kubectl exec -it vm-0 /bin/bash $ kubectl exec -it vm-0 /bin/sh
vm-0 # apt-get update
...
vm-0 # apt-get install curl -y
vm-0 # curl -sSL -o /peer-finder https://storage.googleapis.com/kubernetes-release/pets/peer-finder vm-0 # curl -sSL -o /peer-finder https://storage.googleapis.com/kubernetes-release/pets/peer-finder
vm-0 # chmod -c 755 peer-finder vm-0 # chmod -c 755 peer-finder
@@ -196,6 +202,9 @@ web-0
If you scale the cluster, the new pods parent themselves to the same master. To test this you can `kubectl edit` the petset and change the `replicas` field to 5: If you scale the cluster, the new pods parent themselves to the same master. To test this you can `kubectl edit` the petset and change the `replicas` field to 5:
```shell ```shell
$ kubectl edit petset web
...
$ kubectl get po -l app=nginx $ kubectl get po -l app=nginx
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
web-0 1/1 Running 0 2h web-0 1/1 Running 0 2h