Change:
Build Kubernetes-Mesos. ```bash <del> $ git clone https://github.com/mesosphere/kubernetes-mesos k8sm $ mkdir -p bin && sudo docker run --rm -v $(pwd)/bin:/target  -v $(pwd)/k8sm:/snapshot -e GIT_BRANCH=release-0.4  mesosphere/kubernetes-mesos:build </del> <ins> $ git clone https://github.com/GoogleCloudPlatform/kubernetes $ cd kubernetes $ export KUBERNETES_CONTRIB=mesos $ make </ins> ``` Set some environment variables. The internal IP address of the master may be obtained via `hostname -i`. ```bash <del> $ export servicehost=$(hostname -i) $ export mesos_master=${servicehost}:5050 $ export KUBERNETES_MASTER=http://${servicehost}:8888 </del> <ins> $ export KUBERNETES_MASTER_IP=$(hostname -i) $ export KUBERNETES_MASTER=http://${KUBERNETES_MASTER_IP}:8888 </ins> ``` ### Deploy etcd Start etcd and verify that it is running: ```bash <del> $ sudo docker run -d --hostname $(uname -n) --name etcd -p 4001:4001 -p 7001:7001 coreos/etcd </del> <ins> $ sudo docker run -d --hostname $(uname -n) --name etcd -p 4001:4001 -p 7001:7001 quay.io/coreos/etcd:v2.0.12 </ins> ``` ```bash $ sudo docker ps <del> CONTAINER ID   IMAGE                COMMAND   CREATED   STATUS   PORTS                NAMES fd7bac9e2301   coreos/etcd:latest   "/etcd"   5s ago    Up 3s    2379/tcp, 2380/...   etcd </del> <ins> CONTAINER ID   IMAGE                        COMMAND   CREATED   STATUS   PORTS                NAMES fd7bac9e2301   quay.io/coreos/etcd:v2.0.12  "/etcd"   5s ago    Up 3s    2379/tcp, 2380/...   etcd </ins> ``` It's also a good idea to ensure your etcd instance is reachable by testing it ```bash <del> curl -L http://$servicehost:4001/v2/keys/ </del> <ins> curl -L http://${KUBERNETES_MASTER_IP}:4001/v2/keys/ </ins> ``` If connectivity is OK, you will see an output of the available keys in etcd (if any). ### Start Kubernetes-Mesos Services <del> Start the kubernetes-mesos API server, controller manager, and scheduler on a Mesos master node: </del> <ins> Update your PATH to more easily run the Kubernetes-Mesos binaries: ```bash $ export PATH="$(pwd)/_output/local/go/bin:$PATH" ``` Identify your Mesos master: depending on your Mesos installation this is either a `host:port` like `mesos_master:5050` or a ZooKeeper URL like `zk://zookeeper:2181/mesos`. In order to let Kubernetes survive Mesos master changes, the ZooKeeper URL is recommended for production environments. ```bash $ export MESOS_MASTER=<host:port or zk:// url> ``` Create a cloud config file `mesos-cloud.conf` in the current directory with the following contents: ```bash $ cat <<EOF >mesos-cloud.conf [mesos-cloud] mesos-master        = ${MESOS_MASTER} EOF ``` Now start the kubernetes-mesos API server, controller manager, and scheduler on the master node: </ins> ```bash <del> $ ./bin/km apiserver  --address=${servicehost}  --mesos_master=${mesos_master}  --etcd_servers=http://${servicehost}:4001  </del> <ins> $ km apiserver  --address=${KUBERNETES_MASTER_IP}  --etcd-servers=http://${KUBERNETES_MASTER_IP}:4001  </ins> --service-cluster-ip-range=10.10.10.0/24  --port=8888  <del> --cloud_provider=mesos  </del> <ins> --cloud-provider=mesos  --cloud-config=mesos-cloud.conf  </ins> --v=1 >apiserver.log 2>&1 & <del> $ ./bin/km controller-manager  --master=$servicehost:8888  --mesos_master=${mesos_master}  </del> <ins> $ km controller-manager  --master=${KUBERNETES_MASTER_IP}:8888  --cloud-provider=mesos  --cloud-config=./mesos-cloud.conf   </ins> --v=1 >controller.log 2>&1 & <del> $ ./bin/km scheduler  --address=${servicehost}  --mesos_master=${mesos_master}  --etcd_servers=http://${servicehost}:4001  --mesos_user=root  --api_servers=$servicehost:8888  </del> <ins> $ km scheduler  --address=${KUBERNETES_MASTER_IP}  --mesos-master=${MESOS_MASTER}  --etcd-servers=http://${KUBERNETES_MASTER_IP}:4001  --mesos-user=root  --api-servers=${KUBERNETES_MASTER_IP}:8888  </ins> --v=2 >scheduler.log 2>&1 & ``` <del> 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  --bind_address=${servicehost}  --etcd_servers=http://${servicehost}:4001  --logtostderr=true >proxy.log 2>&1 & ``` </del> Disown your background jobs so that they'll stay running if you log out. ```bash

Discussion:
Hi We are updating docs to v1beta3. v1beta1 and v1beta2 will be abandoned soon. For the examples in getting-started-guides, we tend to use hyperlinks to point to examples instead of letting them have their own individual examples (see ). However, in the mesos guide, the examples contain mesos specific setup and knowledge, so I can't simply remove the texts and point to kubernetes/examples/guestbook, which is updated to v1beta3. My suggestion is that we update the guestbook example in kubernetes-mesos, and use a hyperlink in mesos getting-started-guide to replace the example texts. Could you help to make the changes? Thanks.
cc
We're going to delete v1beta1 and v1beta2 in O(days). See PR .
cc
we've initiated an effort to upstream some components into k8s. as part of that effort, we're upgrading the guestbook examples for k8s-mesos: the getting started guide for mesos will likely have to change in order to align with the move upstream. tracking this issue here: , Brian Grant wrote:
xref , James DeFelice wrote:
Ref
cc
xref
This needs to be moved to the v1 API.
Agreed. We have changes in review right now, should be merged soon. , Brian Grant wrote: