Guestbook README updates, reset-by-peer error message and v1beta3 note

duda · Mar 4, 2015 · 3a0a4f1 · 3a0a4f1
1 parent cb1e044
commit 3a0a4f1
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/examples/guestbook/README.md b/examples/guestbook/README.md
@@ -22,7 +22,9 @@ See the companion [Setup Kubernetes](https://github.com/GoogleCloudPlatform/kube
 Note: This redis-master is *not* highly available.  Making it highly available would be a very interesting, but intricate exercise - redis doesn't actually support multi-master deployments at the time of this writing, so high availability would be a somewhat tricky thing implement, and might involve periodic serialization to disk, and so on.
 
 Use (or just create) the file `examples/guestbook/redis-master-controller.json` which describes a single pod running a redis key-value server in a container:
-Note that, although the redis server runs just with a single replica, we use replication controller to enforce that exactly one pod keeps running (e.g. in a event of node going down, the replication controller will ensure that the redis master gets restarted on a healthy node). 
+Note that, although the redis server runs just with a single replica, we use replication controller to enforce that exactly one pod keeps running (e.g. in a event of node going down, the replication controller will ensure that the redis master gets restarted on a healthy node).   This could result in data loss.
+
+** These json files are for v1beta1.  See the v1beta3/ folder for updated equivalents.**
 
 ```js
 {
@@ -463,8 +465,7 @@ When you go to localhost:8000, you might not see the page at all.  Testing it wi
 ```shell
    ==> default: curl: (56) Recv failure: Connection reset by peer
 ```
-
-This means the web frontend isn't up yet.  Wait a while, possibly about 2 minutes or more, depending on your set up. Also, run a *watch* on docker ps, to see if containers are cycling on and off or not starting.
+This means the web frontend isn't up yet. Specifically, the  "reset by peer" message is occuring because you are trying to access the *right port*, but *nothing is bound* to that port yet. Wait a while, possibly about 2 minutes or more, depending on your set up. Also, run a *watch* on docker ps, to see if containers are cycling on and off or not starting.
 
 ```watch 
 $> watch -n 1 docker ps