From e933ac5784228ab9550aa3a3d6c48ec846f99261 Mon Sep 17 00:00:00 2001
From: Joe Beda <joe.github@bedafamily.com>
Date: Tue, 16 Dec 2014 14:21:22 -0800
Subject: [PATCH] Make it clearer how to run kubectl after bringing up a local
 cluster.

Fixes #2935.
---
 hack/local-up-cluster.sh | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/hack/local-up-cluster.sh b/hack/local-up-cluster.sh
index 556ad6f8e7c..c7d7cb66c1e 100755
--- a/hack/local-up-cluster.sh
+++ b/hack/local-up-cluster.sh
@@ -128,13 +128,21 @@ SCHEDULER_LOG=/tmp/kube-scheduler.log
   --master="http://${API_HOST}:${API_PORT}" >"${SCHEDULER_LOG}" 2>&1 &
 SCHEDULER_PID=$!
 
-echo "Local Kubernetes cluster is running. Press Ctrl-C to shut it down."
-echo "Logs: "
-echo "  ${APISERVER_LOG}"
-echo "  ${CTLRMGR_LOG}"
-echo "  ${KUBELET_LOG}"
-echo "  ${PROXY_LOG}"
-echo "  ${SCHEDULER_LOG}"
+cat <<EOF
+Local Kubernetes cluster is running. Press Ctrl-C to shut it down.
+
+Logs:
+  ${APISERVER_LOG}
+  ${CTLRMGR_LOG}
+  ${KUBELET_LOG}
+  ${PROXY_LOG}
+  ${SCHEDULER_LOG}
+
+To start using your cluster, open up another terminal/tab and run:
+
+  export KUBERNETES_PROVIDER=local
+  cluster/kubectl.sh
+EOF
 
 cleanup()
 {