-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose image cache option in DSL (and other POD/container configuration options). #516
Comments
Can we use strong hashes to avoid image name collisions instead? Assuming mutable images can be dangerous and lead to hard to debug bugs. |
Sure. For the sample components, we could certainly use the hashes. In fact, This PR(#571) changed the sample components to hashes. |
It makes sense to me to expose POD/container features in the DSL. Is there a way we could expose all these features all at once? |
we already support the imagepullpolicy: pipelines/sdk/python/kfp/dsl/_container_op.py Line 370 in 895645c
|
I've enabled the
I am using minikf
|
I'm not exactly following. How did you validate that the image being actually used is not the latest one? |
I have a
|
Argo by default reuses images, which might cause unexpected errors. For example, users author a component and update the component while the pipeline is still using the old image cached by argo. Maybe the DSL should provide an option to not use the cached image.
WDYT
The text was updated successfully, but these errors were encountered: