From 9e9b44ecfe829db0982400588fdf5717100a907a Mon Sep 17 00:00:00 2001 From: Manas Srivastava Date: Sat, 30 May 2026 16:49:23 +0530 Subject: [PATCH] =?UTF-8?q?ci:=20bump=20kubectl=20rollout-status=20timeout?= =?UTF-8?q?=20180s=20=E2=86=92=20300s?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Today's api #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). Worker has the same pattern. Bumping to 300s removes the false-failure rerun cycle. Same change ships simultaneously in api + provisioner deploy.yml. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/deploy.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index ce5f209..16ce710 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -176,10 +176,14 @@ jobs: "deployment/${K8S_DEPLOYMENT}" \ "${K8S_CONTAINER}=${IMAGE}" \ -n "${K8S_NAMESPACE}" + # 2026-05-30: bumped 180s → 300s after a real api rollout took + # ~240s (image pull + readiness on a fresh node) and the workflow + # timed out even though the pod came up healthy. Same change in + # api + provisioner deploy.yml. False-failure forces a manual rerun. kubectl rollout status \ "deployment/${K8S_DEPLOYMENT}" \ -n "${K8S_NAMESPACE}" \ - --timeout=180s + --timeout=300s - name: Verify rolled-out image tag matches built version # The worker has no public ingress, so we can't curl an external