From 1d850e84279c8fb57d1bdcecc8659e911a13cf35 Mon Sep 17 00:00:00 2001
From: Ed Bartosh <eduard.bartosh@intel.com>
Date: Sun, 22 Mar 2026 18:41:51 +0200
Subject: [PATCH] localupcluster: set readiness polling interval to 1 second

Without an explicit interval, Gomega's default polling is very frequent,
generating a large volume of /readyz and /healthz requests in the component
logs. Set an explicit 1-second interval to reduce noise while still
detecting readiness promptly.
---
 test/utils/localupcluster/localupcluster.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/utils/localupcluster/localupcluster.go b/test/utils/localupcluster/localupcluster.go
index 3191b20166c..f3a71c3e537 100644
--- a/test/utils/localupcluster/localupcluster.go
+++ b/test/utils/localupcluster/localupcluster.go
@@ -531,7 +531,7 @@ func (c *Cluster) checkEndpoint(tCtx ktesting.TContext, cmd *Cmd, scheme, hostIP
 			return fmt.Errorf("%s returned %d, waiting for 200", url, resp.StatusCode)
 		}
 		return nil
-	}).Should(gomega.Succeed(), fmt.Sprintf("HTTP GET %s", url))
+	}).WithPolling(time.Second).Should(gomega.Succeed(), fmt.Sprintf("HTTP GET %s", url))
 }
 
 func dumpProcesses(tCtx ktesting.TContext) {