github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-01 17:29:00 +00:00
Code Issues Projects Releases Wiki Activity

Fix inconsistent capitalization in guestbook example README

Browse Source
This commit is contained in:
Tim St. Clair
2015-06-08 14:40:50 -07:00
parent 5aa0219ada
commit 0cc7186f17
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
examples/guestbook/README.md
View File

@@ -153,7 +153,7 @@ This will cause all pods to see the redis master apparently running on <ip>:6379
Thus, once created, the service proxy on each minion is configured to set up a proxy on the specified port (in this case port 6379).
### Step Three: Fire up the replicated slave pods
Although the redis master is a single pod, the redis read slaves are a 'replicated' pod. In Kubernetes, a replication controller is responsible for managing multiple instances of a replicated pod. The replicationController will automatically launch new Pods if the number of replicas falls (this is quite easy - and fun - to test, just kill the docker processes for your pods at will and watch them come back online on a new node shortly thereafter).
Although the redis master is a single pod, the redis read slaves are a 'replicated' pod. In Kubernetes, a replication controller is responsible for managing multiple instances of a replicated pod. The replication controller will automatically launch new pods if the number of replicas falls (this is quite easy - and fun - to test, just kill the docker processes for your pods at will and watch them come back online on a new node shortly thereafter).
Use the file `examples/guestbook/redis-slave-controller.json`, which looks like this: