github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

guestbook: s/services/tasks/

pull/6/head
Johan Euphrosine 2014-06-07 02:02:32 -07:00
parent f528ef8018
commit 859f5a1552
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
examples/guestbook/guestbook.md
View File

@ -73,7 +73,7 @@ cluster/cloudcfg.sh -c redis-master-service.json create /services
Once created, the service proxy on each minion is configured to set up a proxy on the specified port (in this case port 10000).
### Step Three: Turn up the replicated slave service.
### Step Three: Turn up the replicated slave tasks.
Although the redis master is a single task, the redis read slaves are a 'replicated' task, in Kubernetes, a replication controller is responsible for managing multiple instances of a replicated task. Create a file named `redis-slave-controller.json` that contains:
```javascript
@ -139,7 +139,7 @@ Now that you have created the service specification, create it in your cluster w
cluster/cloudcfg.sh -c redis-slave-service.json create /services
```
### Step Five: Create the frontend service.
### Step Five: Create the frontend task.
This is a simple PHP server that is configured to talk to both the slave and master services depdending on if the request is a read or a write. It exposes a simple AJAX interface, and serves an angular based U/X. Like the redis read slaves it is a replicated service instantiated by a replication controller. Create a file named `frontend-controller.json`: