You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and no matter what I try, kubeflow keeps caching the steps which makes no sense since our underlying data changes, but the parameters are the same. Also tried all of the suggestions here, including modifying the mutating admission webhook, but nothing works:
The only thing that sort-of works is reverting kubeflow pipelines back to 2.0.5. The annotations are then still there, but somehow kubeflow ignores them and doesn't cache with that version.
Expected result
Kubeflow stops caching when I ask it to.
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered:
Hm, I'll look into this. I can verify that the annotations are not used in 2.0.5, which is coincidentally the version that I tend to run. The only thing that matters is in 2.0.5 the enableCache option in the proto. The check is here.
Environment
How did you deploy Kubeflow Pipelines (KFP)?
Using Kustomize, in GKE
KFP version:
Pipelines version 2.2.0
KFP SDK version:
SDK version 1.8.22 and 2.7.0 (both have this issue)
Steps to reproduce
I have a pipeline like this:
When compiling this pipeline, the Pod still gets these annotations
and no matter what I try, kubeflow keeps caching the steps which makes no sense since our underlying data changes, but the parameters are the same. Also tried all of the suggestions here, including modifying the mutating admission webhook, but nothing works:
#4857
https://www.kubeflow.org/docs/components/pipelines/v1/overview/caching/
https://www.kubeflow.org/docs/components/pipelines/v2/caching/
The only thing that sort-of works is reverting kubeflow pipelines back to 2.0.5. The annotations are then still there, but somehow kubeflow ignores them and doesn't cache with that version.
Expected result
Kubeflow stops caching when I ask it to.
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: