Closed rimolive closed 9 months ago
Hi @rimolive ,
please suggest on timelines when the changes will be implemented.
thanks.
It would be great If you parametrize driver image also
@nirajkl @and-1 Please check latest status. We have an ongoing PR to introduce launcher and driver image parametrization.
This was implemented and released in KFP 2.0.5
I want to highlight that V2_LAUNCHER_IMAGE
will NOT affect V2_COMPATIBLE
mode runs.
These runs will still use the _DEFAULT_LAUNCHER_IMAGE
which was hard-coded in the version of the kfp
SDK you are using which is usually gcr.io/ml-pipeline/kfp-launcher:1.8.7
:
kfp==2.7.0
kfp==1.8.7
v2-compatible mode is no longer supported, and the ideal path is upgrade kfp to the latest release. We're currently in 2.1.0 but we're planning to release 2.2.0 for Kubeflow 1.9.
Feature Area
/area backend
What feature would you like to see?
Launcher image could be parametrized in a way that users can make use of the following tasks:
What is the use case or pain point?
Launcher image is hard-coded, and this is bad practice IMHO. We should be able to let users parameterize any image used by KFP, and launcher image is that example.
Is there a workaround currently?
There is no possible workarounds
Love this idea? Give it a 👍.