Learn More
Resend Email
5
b2plane
2y

1. Updated kubernetes shit image
2. For hours cant figure out why shits showing v1 instead of v2
3. Thought it was caching shit
4. Ran --no-cache command to fix this shit
5. Wasted half a day to debug this shit
6. Turns out in kubernetes deployment yaml there was imagePullPolicy set to IfNotPresent, instead of Always. The shit wasnt pulling the v2 because the image (v1) was already present. This shit blows my mind

rant
Favorite
Ranter
Comments
  • 0
    2y
    Did you update the docker tag or create a new one and deployed the new one?
  • 0
    2y
    @hypervtechnics i just set a new image name and deployed it like that. Didnt touch tags. Nothing was wrong. It just wasnt pulling the latest image that was pushed to docker hub
  • 1
    2y
    But why should kubernetes automatically pick up a completely different image? Did you just update the latest tag or something?
  • 0
    2y
    @hypervtechnics because i kubectl apply -f pods/deployment.yml which has defined to pick up the latest image. But it wasnt picking up because deployment.yml wasnt set to pull policy to Always
  • 1
    2y
    Yeah cause thats not how docker image tags are meant to be used ;)
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment