Skip to content

Commit 8de5c0b

Browse files
[hotfix][e2e] Mitigate flaky minikube ingress addon enable in CI (#1107)
1 parent 640b436 commit 8de5c0b

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

e2e-tests/utils.sh

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -296,6 +296,18 @@ function start_minikube {
296296
echo "Could not start minikube. Aborting..."
297297
exit 1
298298
fi
299+
if ! retry_times 3 30 enable_minikube_ingress; then
300+
echo "Could not enable minikube ingress addon. Aborting..."
301+
exit 1
302+
fi
303+
}
304+
305+
function enable_minikube_ingress {
306+
# `minikube addons enable ingress` performs its own synchronous verify with
307+
# an internal ~3m deadline that is frequently exceeded on cold CI runners
308+
# while pulling the ingress-nginx controller and webhook-certgen images.
309+
# The addon Deployment is applied even when verify times out, so retrying
310+
# is cheap and idempotent: the second attempt reuses the cached images.
299311
minikube addons enable ingress
300312
}
301313

0 commit comments

Comments
 (0)