- Shipped
- September 5, 2026 at 4:37 PM UTC
- Author
- Kamo
- Commit
- 3731133
The image is tagged with the commit SHA, so rebuilding the same commit produces an identical image reference. `kubectl set image` then changes nothing, the Deployment is never touched, `rollout status` succeeds immediately against the OLD pods, and this pipeline reports a successful deploy having deployed nothing. That is the normal case whenever a service must be rebuilt to pick up a kamo-shared-library change without a commit of its own — and it is invisible, because the image tag everyone checks to confirm a deploy is exactly the thing guaranteed to look correct while the pods run stale code. It happened twice yesterday and both times was found only by comparing digests by hand. The step now compares the image reference before and after, and forces a rollout restart when it is unchanged so the new content behind that tag is pulled.