capri-xiyue

> This sounds very similar to #1654. > > Will do a bit more digging before I mark this as a dupe. I think I use key-full signing instead of...

> What version of cosign did you notice this in? 👀 1.5.2

@zijianjoy I talked with sdk side and vertex side, the agreement is to implement disable/enable caching level at client side first. Later when we have a clear goal of caching...

> @capri-xiyue Sounds good on providing the ability to disable pipeline level caching on UI side, once we updated pipeline job proto to support this field. But question: currently when...

Discussed offline, backend needs to expose cache configuration first and then front end can disable caching for a particular pipeline run via the UI

Reassigned it to James Wu to further discuss the priority and the assignee

Reassigned it to James Wu to further discuss the priority

/retest

reassigned it to @chensun

The workaround is to call GET /apis/v1beta1/runs/{run_id} https://www.kubeflow.org/docs/components/pipelines/reference/api/kubeflow-pipeline-api-spec/#operation--apis-v1beta1-runs--run_id--get and check the apiPipelineRuntime field. KFP V2 will support this feature.