Thore CimbalandClaude Sonnet 5
62b05c51c4
Auto-Deploy on Push / verify-and-notify (push) Canceled after 0s
Discovered live: the default RollingUpdate strategy tries to schedule the new pod before removing the old one, which can never succeed for a hostNetwork Deployment on a single-node cluster (both pods would need the same node ports 3478/5349 simultaneously). Surfaced by the rotated-at annotation bump from the previous commit getting stuck in FailedScheduling. Recreate kills the old pod first, freeing the ports. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>