From 173eb8bf434ae0cef113ea5b642c094df00c2b1d Mon Sep 17 00:00:00 2001 From: Mike Kolesnik Date: Wed, 29 Oct 2025 13:21:29 +0200 Subject: [PATCH] Increase e2e timeout when waiting for service LB When running in KIND this is fine, but sometimes when running in a "real" cloud environment, this can cause unnecessary test failures due to timing out before the LB is up and running. Signed-off-by: Mike Kolesnik --- tests/e2e/util/common/e2e_utils.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/e2e/util/common/e2e_utils.go b/tests/e2e/util/common/e2e_utils.go index c950f44895..ff5e289d16 100644 --- a/tests/e2e/util/common/e2e_utils.go +++ b/tests/e2e/util/common/e2e_utils.go @@ -109,7 +109,7 @@ func GetSVCLoadBalancerAddress(ctx context.Context, cl client.Client, ns, svcNam Eventually(func() ([]corev1.LoadBalancerIngress, error) { err := cl.Get(ctx, client.ObjectKey{Namespace: ns, Name: svcName}, svc) return svc.Status.LoadBalancer.Ingress, err - }, "1m", "1s").ShouldNot(BeEmpty(), "LoadBalancer should be ready") + }, "3m", "1s").ShouldNot(BeEmpty(), "LoadBalancer should be ready") if svc.Status.LoadBalancer.Ingress[0].IP != "" { return svc.Status.LoadBalancer.Ingress[0].IP