get-kube-local.sh checks pods with option "--namespace=kube-system"

Local cluster creation using get-kube-local.sh is never finished. The get-kube-local.sh monitors running_count of pods such as etcd, master and kube-proxy, but these pods are created under the namespace kube-system. Therefore kubectl can't find these pods then cluster creation isn't completed. The get-kube-local.sh should monitor created pods with option "--namespace=kube-system". Fix #42517

get-kube-local.sh checks pods with option "--namespace=kube-system"
fe5f7a76 · mtanino · 2d319bd4 · fe5f7a76
Commit fe5f7a76 authored Mar 03, 2017 by mtanino
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

get-kube-local.sh cluster/get-kube-local.sh +1 -1

No files found.
--- a/cluster/get-kube-local.sh
+++ b/cluster/get-kube-local.sh
@@ -80,7 +80,7 @@ function create_cluster {
  echo -e -n "\tWaiting for master components to start..."
  while true; do
-    local running_count=$(kubectl -s=http://${KUBE_HOST}:8080 get pods --no-headers 2>/dev/null | grep "Running" | wc -l)
+    local running_count=$(kubectl -s=http://${KUBE_HOST}:8080 get pods --no-headers --namespace=kube-system 2>/dev/null | grep "Running" | wc -l)
    # We expect to have 3 running pods - etcd, master and kube-proxy.
    if [ "$running_count" -ge 3 ]; then
      break