Durable first-party example
Kubernetes rollout stuck on a mutable latest tag
A deployment behavior explainer that shows why a cluster can sync successfully while pods keep running an old image digest.
A release engineering explainer for mutable container tags and pod template rollouts.
Founders, operators, and engineers reviewing a production deployment.
A GitOps sync looked green, but the deployment pod template did not change because the image tag stayed the same.
A public explainer URL gives the landing session, operator notes, and future task context one durable reference instead of a private terminal transcript.
The misleading signal
The deploy system applied the latest manifests and reported success. Kubernetes did not restart pods because the rendered deployment spec was unchanged.
The durable fix
Use immutable image tags or another pod-template-changing value so every release creates a new ReplicaSet without a manual restart.
Why the explainer helps
The issue sits between CI, registry, GitOps, and Kubernetes behavior. A stable explainer gives each reviewer the same mental model before changing the deploy path.