Title
#plugins-integrations
Goss

Goss

09/26/2022, 2:47 PM
Problem with Kubeflow Pipeline not using the most recent image. So kedro-kubeflow by default wants to use
latest
as the image version. In theory, if
imagePullPolicy
is Always, KFP should check the registry to see if the sha on the image has changed and repull the image when provisioning a new container. This is not happening like it should--I can see KFP using a new container (via a new
containerId
) but the sha of the image used does not update to the latest in the repository. I have also applied
Always
as the
imagePullPolicy
for the node in question (even though I think that is already inherited). Still it doesn't work. I could switch to semantic versioning of the image (instead of
latest
) BUT it seems like Kedro is designed to work with
latest
and also that will lead to a build-up of images in the registry (at least in the development stage). Does anyone know what might be going on here or how to get KFP to use the most recent image when using
latest
versioning?