Skip to content

K
k3s
Commit 00960b4d authored by Klaus Ma's avatar Klaus Ma
Browse files
Options

Using API_HOST_IP to do apiserver health check.

parent b9bb440b
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
hack/local-up-cluster.sh
View file @ 00960b4d
...@@ -439,7 +439,7 @@ function start_apiserver { ...@@ -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 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. # this matches what happened with the combination in 1.4.
# TODO change this conditionally based on whether API_PORT is on or off # 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 ; } || { echo "check apiserver logs: ${APISERVER_LOG}" ; exit 1 ; }
# Create kubeconfigs for all components, using client certs # Create kubeconfigs for all components, using client certs
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment