From 790011430395459649966e4b7f814748017cb74a Mon Sep 17 00:00:00 2001 From: tusuii Date: Sat, 28 Feb 2026 00:07:55 +0530 Subject: [PATCH] fix: increase MetalLB speaker daemonset rollout timeout to 180s MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Speaker runs on all 3 nodes and needs image pull + startup time per node. 90s was too tight — bumped to 180s to handle slow node startups. Co-Authored-By: Claude Sonnet 4.6 --- Jenkinsfile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Jenkinsfile b/Jenkinsfile index 75dcd07..16dd557 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -118,8 +118,9 @@ pipeline { kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.8/config/manifests/metallb-native.yaml # Wait for MetalLB controller and speaker to be ready - kubectl rollout status deployment/controller -n metallb-system --timeout=90s - kubectl rollout status daemonset/speaker -n metallb-system --timeout=90s + # speaker is a DaemonSet on all 3 nodes — give it extra time + kubectl rollout status deployment/controller -n metallb-system --timeout=120s + kubectl rollout status daemonset/speaker -n metallb-system --timeout=180s # Apply IP pool config — CRDs must be ready before this kubectl apply -f k8s/overlays/on-premise/metallb/