From a9473cb6b95751527702d89b68edfe4c71ac5e29 Mon Sep 17 00:00:00 2001 From: Davanum Srinivas Date: Fri, 2 Feb 2018 14:28:56 -0500 Subject: [PATCH] Ability to run an external binary instead of hyperkube cloud-controller-manager Since we want folks to test their own binaries, let's allow a way for them them to specify a custom binary. --- hack/local-up-cluster.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hack/local-up-cluster.sh b/hack/local-up-cluster.sh index 22fb06e4736..1201a83b458 100755 --- a/hack/local-up-cluster.sh +++ b/hack/local-up-cluster.sh @@ -66,6 +66,7 @@ WAIT_FOR_URL_API_SERVER=${WAIT_FOR_URL_API_SERVER:-20} ENABLE_DAEMON=${ENABLE_DAEMON:-false} HOSTNAME_OVERRIDE=${HOSTNAME_OVERRIDE:-"127.0.0.1"} EXTERNAL_CLOUD_PROVIDER=${EXTERNAL_CLOUD_PROVIDER:-false} +EXTERNAL_CLOUD_PROVIDER_BINARY=${EXTERNAL_CLOUD_PROVIDER_BINARY:-""} CLOUD_PROVIDER=${CLOUD_PROVIDER:-""} CLOUD_CONFIG=${CLOUD_CONFIG:-""} FEATURE_GATES=${FEATURE_GATES:-"AllAlpha=false"} @@ -647,7 +648,7 @@ function start_cloud_controller_manager { fi CLOUD_CTLRMGR_LOG=${LOG_DIR}/cloud-controller-manager.log - ${CONTROLPLANE_SUDO} "${GO_OUT}/hyperkube" cloud-controller-manager \ + ${CONTROLPLANE_SUDO} ${EXTERNAL_CLOUD_PROVIDER_BINARY:-"${GO_OUT}/hyperkube" cloud-controller-manager} \ --v=${LOG_LEVEL} \ --vmodule="${LOG_SPEC}" \ ${node_cidr_args} \