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
The root cause is argoproj/argo-workflows#6022 introduced a behavior change that the content of Argo workflow template is no longer logged under pod.metadata.annotations, instead it puts the template in container env.
The change was released in Argo workflow v3.2.0-rc1. And #6920 upgraded Argo workflow used in KFP from 3.1.14 to 3.2.3. The change broke v1 caching implementation because it relies on Argo workflow template present in pod.metadata.annotations.
The text was updated successfully, but these errors were encountered:
The root cause is argoproj/argo-workflows#6022 introduced a behavior change that the content of Argo workflow template is no longer logged under
pod.metadata.annotations
, instead it puts the template in container env.The change was released in Argo workflow v3.2.0-rc1. And #6920 upgraded Argo workflow used in KFP from
3.1.14
to3.2.3
. The change broke v1 caching implementation because it relies on Argo workflow template present inpod.metadata.annotations
.The text was updated successfully, but these errors were encountered: