Merge pull request #6938 from inteon/remove_docker_network_hack
Remove docker custom network hack which has been moved to the test runner
This commit is contained in:
commit
066ed9045d
@ -123,26 +123,6 @@ if [ -n "$show_image" ]; then
|
||||
fi
|
||||
|
||||
setup_kind() {
|
||||
# When running in our CI environment the Docker network's subnet choice will
|
||||
# cause issues with routing, which can manifest in errors such as this one:
|
||||
#
|
||||
# dial tcp: lookup charts.jetstack.io on 10.8.240.10:53: read udp 10.8.0.2:54823->10.8.240.10:53: i/o timeout
|
||||
#
|
||||
# as seen in the build [1]. We create this custom network as a workaround
|
||||
# until we have a way to properly patch this.
|
||||
#
|
||||
# [1]: https://prow.build-infra.jetstack.net/view/gs/jetstack-logs/pr-logs/pull/cert-manager_approver-policy/36/pull-cert-manager-approver-policy-smoke/1447565895923666944#1:build-log.txt%3A222
|
||||
if printenv CI >/dev/null; then
|
||||
if ! docker network inspect kind >/dev/null 2>&1; then
|
||||
docker network create --driver=bridge --subnet=192.168.0.0/16 --gateway 192.168.0.1 kind
|
||||
fi
|
||||
|
||||
# Wait for the network to be created so kind does not overwrite it.
|
||||
while ! docker network inspect kind >/dev/null; do
|
||||
sleep 100ms
|
||||
done
|
||||
fi
|
||||
|
||||
# (1) Does the kind cluster already exist?
|
||||
if ! kind get clusters -q | grep -q "^$kind_cluster_name\$"; then
|
||||
trace kind create cluster --config "make/config/kind/cluster.yaml" \
|
||||
|
||||
Loading…
Reference in New Issue
Block a user