subodh/scrum-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: increase MetalLB speaker daemonset rollout timeout to 180s

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
tusuii
2026-02-28 00:07:55 +05:30
parent 69f7b4a93d
commit 7900114303
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Jenkinsfile vendored
View File

@@ -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/