A municipal 311 API tags every push as latest and production Pods flip unpredictably between builds. What change makes application releases reproducible?
Select an answer to reveal the explanation.
Short Explanation
latest is like labeling every jar in the pantry "food"—you never know what you are opening. Pin a real version tag or digest so Monday's deploy and Friday's restart serve the same bits.
Full Explanation
Floating tags such as latest resolve to different digests over time, so Pods created later can run different code than earlier replicas. Application Deployments should reference an explicit tag or, better, an image digest for immutability. Renaming workloads or disabling pulls does not provide reproducible release identity.