Fixed error in Mesos getting started guide.

The instructions previously advised that the Kubernetes-Mesos executor
will not start up a proxy instance on each minion, but this is
incorrect.  Changed the wording to indicate that the proxy only needs to
be started manually on the master.
This commit is contained in:
Connor Doyle 2015-04-16 13:26:08 -07:00
parent 9b68984104
commit a6d0b44a33

View File

@ -88,8 +88,9 @@ $ ./bin/km scheduler \
--v=2 >scheduler.log 2>&1 &
```
Kubernetes-mesos will start up kubelets automatically, but currently the service
proxy needs to be started manually. Start the service proxy on each Mesos slave:
Also on the master node, we'll start up a proxy instance to act as a
public-facing service router, for testing the web interface a little
later on.
```bash
$ sudo ./bin/km proxy \