ci: bump kubectl rollout-status timeout 180s → 300s#199
Merged
Conversation
Today's #198 deploy timed out at 180s even though the new ReplicaSet came up healthy (rollout actually took ~240s on a fresh node with a cold image pull). The job exited red, prod was correct, and the false-failure forced a manual rerun + on-call investigation. Bumping to 300s removes the rerun cycle. Same change ships simultaneously in worker + provisioner deploy.yml. Healthz verify loop extended 6×5s → 12×5s for the same reason: if rollout takes the full timeout, the new pods are only just live when verify starts and the public LB needs a few seconds to route. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mastermanas805
force-pushed
the
ci/bump-rollout-timeout-300s
branch
from
May 30, 2026 11:22
10ad4dc to
3c9da05
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Today's PR #198 (CORS fix) deploy timed out at 180s even though the new ReplicaSet came up healthy. The rollout actually took ~240s on a fresh node with a cold image pull. The job exited red, prod was correct, and the false-failure forced a manual rerun + on-call investigation (memory:
feedback_verify_live_not_just_local).What
kubectl rollout status … --timeout=180s→--timeout=300sSurface (rule 22)
Same change shipping simultaneously in:
Coverage (rule 17)
YAML-only, no binary change. CI itself is the gate — the next master deploy will exercise the new timeout. No new unit tests required (no Go diff).
Symptom: `error: timed out waiting for the condition` after 180s, despite Ready pods
Enumeration: `grep -rn 'timeout=' .github/workflows/` → 1 hit per repo
Sites found: 3 (api, worker, provisioner)
Sites touched: 3
Coverage test: n/a — workflow change
Live verified: pending next master deploy