fix: force deployment rollout when updating task definition #45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/force-rollout-on-taskdef-update"
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?
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