The redis slave configures itself by looking for the Kubernetes service environment variables in the container environment. In particular, the redis slave is started with the following command:
The redis slave configures itself by looking for the Kubernetes service environment variables in the container environment. In particular, the redis slave is started with the following command:
...
@@ -225,7 +225,7 @@ The pod is described in the file `examples/guestbook/frontend-controller.json`:
...
@@ -225,7 +225,7 @@ The pod is described in the file `examples/guestbook/frontend-controller.json`:
```js
```js
{
{
"id":"frontendController",
"id":"frontend-controller",
"kind":"ReplicationController",
"kind":"ReplicationController",
"apiVersion":"v1beta1",
"apiVersion":"v1beta1",
"desiredState":{
"desiredState":{
...
@@ -235,7 +235,7 @@ The pod is described in the file `examples/guestbook/frontend-controller.json`:
...
@@ -235,7 +235,7 @@ The pod is described in the file `examples/guestbook/frontend-controller.json`:
"desiredState":{
"desiredState":{
"manifest":{
"manifest":{
"version":"v1beta1",
"version":"v1beta1",
"id":"frontendController",
"id":"frontend-controller",
"containers":[{
"containers":[{
"name":"php-redis",
"name":"php-redis",
"image":"kubernetes/example-guestbook-php-redis",
"image":"kubernetes/example-guestbook-php-redis",
...
@@ -258,12 +258,12 @@ Using this file, you can turn up your frontend with:
...
@@ -258,12 +258,12 @@ Using this file, you can turn up your frontend with:
Once that's up (it may take ten to thirty seconds to create the pods) you can list the pods in the cluster, to verify that the master, slaves and frontends are running:
Once that's up (it may take ten to thirty seconds to create the pods) you can list the pods in the cluster, to verify that the master, slaves and frontends are running: