From 00960b4d71637dca6c6510f70c775a3af3cd203a Mon Sep 17 00:00:00 2001 From: Klaus Ma Date: Mon, 6 Feb 2017 04:22:20 +0800 Subject: [PATCH] Using API_HOST_IP to do apiserver health check. --- hack/local-up-cluster.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hack/local-up-cluster.sh b/hack/local-up-cluster.sh index c32b76931d2..a1b662709d6 100755 --- a/hack/local-up-cluster.sh +++ b/hack/local-up-cluster.sh @@ -439,7 +439,7 @@ function start_apiserver { # this uses the API port because if you don't have any authenticator, you can't seem to use the secure port at all. # this matches what happened with the combination in 1.4. # TODO change this conditionally based on whether API_PORT is on or off - kube::util::wait_for_url "http://${API_HOST}:${API_PORT}/version" "apiserver: " 1 ${WAIT_FOR_URL_API_SERVER} \ + kube::util::wait_for_url "http://${API_HOST_IP}:${API_PORT}/version" "apiserver: " 1 ${WAIT_FOR_URL_API_SERVER} \ || { echo "check apiserver logs: ${APISERVER_LOG}" ; exit 1 ; } # Create kubeconfigs for all components, using client certs