How ensure Kubernetes pulls correct new image and why avoid :latest?
Tests immutable tagging and Kubernetes image pull behavior. Strong answers demand unique tags like git SHA, explicit deployment spec updates, and explain :latest's reproducibility failures across nodes.
Tests whether you understand immutable infrastructure and Kubernetes image caching. A great answer recommends tagging every build with a unique identifier like the git commit SHA, then updating the deployment manifest to reference that exact tag. It covers :latest downsides: nodes cache different versions, rollbacks are impossible, and you cannot tell what code is running. It notes imagePullPolicy defaults to IfNotPresent for specific tags, so changing the spec triggers the rollout.
Read the original → kubernetes.io
- #kubernetes
- #docker
- #cicd
- #deployment
- #immutable-infrastructure
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.