Hi, is there a way to configure the

imagePullPolicy

on azure when a pod spins up? currently it is set to

IfNotPresent

, but i would like to change that.

@bitter-orange-8782 - the pull policy is a function of how you have defined the image. If you define the image with a tag (and not

latest

) - the policy is set to

IfNotPresent

, otherwise it is set to

Always

We are setting the image tag based on git branch, so it’s not static. (Each developer with his image tags) From the Kubernetes yaml I see that it was set to IfNotPresent. Let’s say I’m running an image with a new tag which is not latest, on my next run with the same tag, should I expect to get the cached image or will it pull again? (Of course its also depends whether the pod get scheduled on the same VM or not)

reusing tags for different versions of the image can potentially lead to unexpected issues (hard to go back in time and debug issues as well). Re: whether the image is cached or will it be pulled again depends on the whether the job is scheduled on the same instance as well as the TTL specified for the cache.

Gotcha, thanks @square-wire-39606 ! 🙏