From a6d0b44a339bf755be37f0246c35040978c5696b Mon Sep 17 00:00:00 2001 From: Connor Doyle Date: Thu, 16 Apr 2015 13:26:08 -0700 Subject: [PATCH] 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. --- docs/getting-started-guides/mesos.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/getting-started-guides/mesos.md b/docs/getting-started-guides/mesos.md index 10f6e7e602..536a7fb4dc 100644 --- a/docs/getting-started-guides/mesos.md +++ b/docs/getting-started-guides/mesos.md @@ -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 \