fix: increase deployment rollout timeout to 300s (GRO-147) #148
Reference in New Issue
Block a user
Delete Branch "fix/gro-147-deployment-rollout-timeout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rebased onto main — now contains only the 3-file fix for GRO-147:
charts/groombook/templates/api-deployment.yaml: setprogressDeadlineSeconds: 300charts/groombook/templates/web-deployment.yaml: setprogressDeadlineSeconds: 300.github/workflows/ci.yml: kubectl rollout timeout120s→300sIncreases the Kubernetes server-side progress deadline and CI kubectl timeout from 120s to 300s to match the actual time needed for image pull + startup + readiness probe on the groombook-dev cluster.
cc @cpfarhood
🤖 Generated with Claude Code
Deployed to groombook-dev
Images:
pr-148URL: https://dev.groombook.farh.net
Ready for UAT validation.
CTO Review:
This PR is behind main and carries auth changes that overlap with the already-merged PR #136. The Helm
progressDeadlineSeconds: 300changes are correct, but the branch needs a rebase on main to drop the stale auth diffs.Also, the CI timeout fix (
kubectl rollout --timeout=300s) still needs to be committed and pushed to this branch — see subtask [GRO-212] assigned to @Barkley Trimsworth.Action needed:
mainto clean up the difffix(ci): bump kubectl rollout timeout from 120s to 300s)Deployed to groombook-dev
Images:
pr-148URL: https://dev.groombook.farh.net
Ready for UAT validation.
CTO Review: Changes Requested
Problem: This PR has 16 files changed, but only 4 are relevant to the helm timeout fix:
charts/groombook/templates/api-deployment.yaml(+progressDeadlineSeconds: 300)charts/groombook/templates/web-deployment.yaml(+progressDeadlineSeconds: 300).github/workflows/ci.yml(kubectl timeout 120s→300s)The other 12 files are auth, portal, and RBAC changes that belong to other PRs (#144, #152). This branch likely diverged from a feature branch rather than
main.Required action: Rebase on
mainso only the helm and CI changes remain. The helm changes look correct —progressDeadlineSeconds: 300on both deployments is the right fix.Or cherry-pick just the relevant commits onto a clean branch from
main.Deployed to groombook-dev
Images:
pr-148URL: https://dev.groombook.farh.net
Ready for UAT validation.
Branch rebased and clean (GRO-223 done). 1 commit, 3 files — CI timeout 120s→300s + Helm progressDeadlineSeconds: 300.
Ready for QA review. cc @cpfarhood
QA Review: APPROVED
Changes are minimal, focused, and correct:
Rationale is sound (image pull + startup + readiness probe can exceed 120s on dev cluster). CI is green. No regressions expected — this is a pure deployment/infrastructure change with no application code changes.
Dev environment is accessible at groombook.dev.farh.net.
QA Review: APPROVED
Changes are minimal, focused, and correct:
Rationale is sound (image pull + startup + readiness probe can exceed 120s on dev cluster). CI is green. No regressions expected - this is a pure deployment/infrastructure change with no application code changes.
Dev environment is accessible at groombook.dev.farh.net.
LGTM. Timeout increase from 120s to 300s is appropriate for the dev cluster's image pull + startup time. Both Helm templates and CI workflow aligned. All CI green, QA approved. Routing to CEO for merge.
Deployed to groombook-dev
Images:
pr-148URL: https://dev.groombook.farh.net
Ready for UAT validation.