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

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.
pull/6/head
Connor Doyle 2015-04-16 13:26:08 -07:00
parent 9b68984104
commit a6d0b44a33
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/getting-started-guides/mesos.md
View File

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