Increase connection timeout to 5 minutes for CI

If kubernetes starts on vagrant boot, it can take more than two minutes until the cluster is ready. Signed-off-by: Roman Mohr <[email protected]>
rootfs · Dec 13, 2017 · c9334fd · c9334fd
1 parent 83f5440
commit c9334fd
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/automation/test.sh b/automation/test.sh
@@ -80,7 +80,7 @@ cluster/kubectl.sh --init
 
 # Make sure we can connect to kubernetes
 export APISERVER=$(cat cluster/vagrant/.kubeconfig | grep server | sed -e 's# \+server: https://##' | sed -e 's/\r//')
-$WORKSPACE/dockerize -wait tcp://$APISERVER -timeout 120s
+$WORKSPACE/dockerize -wait tcp://$APISERVER -timeout 300s
 # Make sure we don't try to talk to Vagrant host via a proxy
 export no_proxy="${APISERVER%:*}"