Commit 10ad4dc
ci: bump kubectl rollout-status timeout 180s → 300s
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>1 parent 1057506 commit 10ad4dc
1 file changed
Lines changed: 9 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
278 | 278 | | |
279 | 279 | | |
280 | 280 | | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
281 | 285 | | |
282 | 286 | | |
283 | 287 | | |
284 | | - | |
| 288 | + | |
285 | 289 | | |
286 | 290 | | |
287 | 291 | | |
| |||
298 | 302 | | |
299 | 303 | | |
300 | 304 | | |
301 | | - | |
302 | | - | |
| 305 | + | |
| 306 | + | |
| 307 | + | |
| 308 | + | |
303 | 309 | | |
304 | 310 | | |
305 | 311 | | |
| |||
0 commit comments