From f56eab28af47d46a67a4e066315ac346dae28053 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 6 Nov 2026 13:31:04 -0500 Subject: [PATCH] Poll for gitea rollout instead of using rollout status `kubectl rollout status` fails immediately once a rollout has exceeded its progress deadline, even if the new pod is about to become ready. Poll the deployment until replicas, updated and available counts agree. Co-Authored-By: Claude Opus 5.5 --- tasks/actions.yaml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/tasks/actions.yaml b/tasks/actions.yaml index 8222188..c0a028a 100644 --- a/tasks/actions.yaml +++ b/tasks/actions.yaml @@ -10,8 +10,16 @@ - name: generate and store a runner registration token when: runner_token_secret.resources | length == 0 block: + # Poll instead of `kubectl rollout status`, which exits immediately once + # a slow rollout has passed the deployment's progressDeadlineSeconds. - name: wait for the gitea deployment to finish rolling out - command: kubectl -n gitea rollout status deployment/gitea --timeout=600s + command: >- + kubectl -n gitea get deployment gitea + -o jsonpath={.spec.replicas},{.status.replicas},{.status.updatedReplicas},{.status.availableReplicas} + register: gitea_rollout + until: gitea_rollout.stdout.split(',') | unique | length == 1 + retries: 90 + delay: 10 changed_when: false - name: generate instance-level runner registration token