(flink-kubernetes-operator) branch main updated: [hotfix][e2e] Mitigate flaky minikube ingress addon enable in CI (#1107)

[gyfora]

This is an automated email from the ASF dual-hosted git repository.

gyfora pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/flink-kubernetes-operator.git


The following commit(s) were added to refs/heads/main by this push:
     new 8de5c0bd [hotfix][e2e] Mitigate flaky minikube ingress addon enable in 
CI (#1107)
8de5c0bd is described below

commit 8de5c0bdbd0fccdaa6c707a276b71495c6d6123d
Author: Dennis-Mircea Ciupitu <dennis.mircea.ciup...@gmail.com>
AuthorDate: Wed Apr 29 18:24:31 2026 +0300

    [hotfix][e2e] Mitigate flaky minikube ingress addon enable in CI (#1107)
---
 e2e-tests/utils.sh | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/e2e-tests/utils.sh b/e2e-tests/utils.sh
index df2eba90..c451c4fa 100755
--- a/e2e-tests/utils.sh
+++ b/e2e-tests/utils.sh
@@ -296,6 +296,18 @@ function start_minikube {
         echo "Could not start minikube. Aborting..."
         exit 1
     fi
+    if ! retry_times 3 30 enable_minikube_ingress; then
+        echo "Could not enable minikube ingress addon. Aborting..."
+        exit 1
+    fi
+}
+
+function enable_minikube_ingress {
+    # `minikube addons enable ingress` performs its own synchronous verify with
+    # an internal ~3m deadline that is frequently exceeded on cold CI runners
+    # while pulling the ingress-nginx controller and webhook-certgen images.
+    # The addon Deployment is applied even when verify times out, so retrying
+    # is cheap and idempotent: the second attempt reuses the cached images.
     minikube addons enable ingress
 }