https://github.com/kubeflow/pipelines/pull/10269 enables administrators to configure the images used for kfp's launcher and driver containers - we need to expose that configuration as charm config so that users can use their own custom images. This is important mainly for airgapped deployments, where these will be pulled from a local container registry.
The UX of this is up to the developer. These could be exposed either each as their own config, or as a dict like in istio-pilot - whichever feels more natural for the UX. The charm should default to the current upstream images.
In completing this task, we must also update tools/get-images.sh to include these images, that way when doing routine scanning or building an airgapped tarball these images are included.
What needs to get done
.
Definition of Done
config for launcher and driver images is exposed
get-images.sh script is updated to include these images
Context
https://github.com/kubeflow/pipelines/pull/10269 enables administrators to configure the images used for kfp's launcher and driver containers - we need to expose that configuration as charm config so that users can use their own custom images. This is important mainly for airgapped deployments, where these will be pulled from a local container registry.
The UX of this is up to the developer. These could be exposed either each as their own config, or as a dict like in istio-pilot - whichever feels more natural for the UX. The charm should default to the current upstream images.
In completing this task, we must also update
tools/get-images.sh
to include these images, that way when doing routine scanning or building an airgapped tarball these images are included.What needs to get done
.
Definition of Done
main