Zarf silently fails to overwrite tagged images in the Zarf Registry about zarf HOT 1 CLOSED

@YrrepNoj and I chatted about this more in slack. The issue here is that the kubelet is not re-pulling the new image from the registry because of it's default behavior. The fix is to either use no tag at all for the image, or a :latest tag

https://kubernetes.io/docs/concepts/containers/images/#updating-images
https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting

When you (or a controller) submit a new Pod to the API server, your cluster sets the imagePullPolicy field when specific conditions are met:

if you omit the imagePullPolicy field, and you specify the digest for the container image, the imagePullPolicy is automatically set to IfNotPresent.

if you omit the imagePullPolicy field, and the tag for the container image is :latest, imagePullPolicy is automatically set to Always;

if you omit the imagePullPolicy field, and you don't specify the tag for the container image, imagePullPolicy is automatically set to Always;

if you omit the imagePullPolicy field, and you specify the tag for the container image that isn't :latest, the imagePullPolicy is automatically set to IfNotPresent.

https://kubernetes.io/docs/concepts/containers/images/#required-image-pull

If you would like to always force a pull, you can do one of the following:

Set the imagePullPolicy of the container to Always.

Omit the imagePullPolicy and use :latest as the tag for the image to use; Kubernetes will set the policy to Always when you submit the Pod.

Omit the imagePullPolicy and the tag for the image to use; Kubernetes will set the policy to Always when you submit the Pod.

Enable the AlwaysPullImages admission controller.

from zarf.