A sanitation routing app republishes the same :v2 tag with new bits, but Pods on some nodes keep the old digest because imagePullPolicy is IfNotPresent. What practice avoids this stale-content trap?
Select an answer to reveal the explanation.
Short Explanation
IfNotPresent plus a recycled tag is like keeping the same library call number after swapping the book inside—some shelves still hold the old copy. Give every release a fresh tag or digest so nodes know they must fetch new content.
Full Explanation
When a tag is mutated in the registry, nodes that already have that name locally will not re-pull under IfNotPresent, leaving Pods on stale digests. Application releases should use unique tags or digests and update the Deployment accordingly. Service deletion or restart annotations do not fix mutable-tag content identity.