fix: force deployment rollout when updating task definition #45

Merged
adam merged 2 commits from fix/force-rollout-on-taskdef-update into main 2026-02-12 21:53:55 -05:00
Owner

When a workload's task definition is updated with the same image tag
(e.g. :latest), Kubernetes skips the rollout because the pod template
hasn't changed. Add a restartedAt annotation to always trigger a
rolling update.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

When a workload's task definition is updated with the same image tag (e.g. :latest), Kubernetes skips the rollout because the pod template hasn't changed. Add a restartedAt annotation to always trigger a rolling update. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix: force deployment rollout when updating task definition
Some checks failed
CI / test-backend (pull_request) Has been cancelled
CI / test-frontend (pull_request) Has been cancelled
8d01708f39
When a workload's task definition is updated with the same image tag
(e.g. :latest), Kubernetes skips the rollout because the pod template
hasn't changed. Add a restartedAt annotation to always trigger a
rolling update.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Merge branch 'main' into fix/force-rollout-on-taskdef-update
All checks were successful
CI / test-backend (pull_request) Successful in 27s
CI / test-frontend (pull_request) Successful in 25s
8de938f30f
adam merged commit 439065eb2e into main 2026-02-12 21:53:55 -05:00
adam deleted branch fix/force-rollout-on-taskdef-update 2026-02-12 21:53:55 -05:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Canpute/canpute-ecs!45
No description provided.