From 5eb30f2762e49f478d0a0fbe702d0578a8c60b69 Mon Sep 17 00:00:00 2001 From: Antonio Ojea Date: Fri, 2 Dec 2022 16:31:20 +0000 Subject: [PATCH] be more strict on network timeouts Change-Id: Ic4044af837047f31e6d60368b79d34dde1adbb98 --- test/e2e/framework/service/const.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/e2e/framework/service/const.go b/test/e2e/framework/service/const.go index f84d02a9e4e..87a75e320df 100644 --- a/test/e2e/framework/service/const.go +++ b/test/e2e/framework/service/const.go @@ -32,9 +32,9 @@ const ( // KubeProxyLagTimeout is the maximum time a kube-proxy daemon on a node is allowed // to not notice a Service update, such as type=NodePort. - // TODO: This timeout should be O(10s), observed values are O(1m), 5m is very + // TODO: This timeout should be O(10s), observed values are O(1m), 2m is very // liberal. Fix tracked in #20567. - KubeProxyLagTimeout = 5 * time.Minute + KubeProxyLagTimeout = 2 * time.Minute // KubeProxyEndpointLagTimeout is the maximum time a kube-proxy daemon on a node is allowed // to not notice an Endpoint update.