[sdk] Missing Alternative for set_ttl_seconds_after_finished in KFP v2

[nasenthi]

Environment

• KFP version: KFP v2
• KFP SDK version: 2.5.0

Steps to reproduce

1. Create and run any pipeline in KFP v2.
2. Observe that the pods created by the run are not automatically deleted after the pipeline execution is complete.

In KFP v1, there was a function kfp.dsl.PipelineConf().set_ttl_seconds_after_finished(seconds) that allowed us to delete pods after a specified time. However, in KFP v2, this function has been deprecated. When attempting to use this deprecated function, we encounter errors as documented in the following issues:

Issue - https://github.com/kubeflow/pipelines/issues/10715 Issue - https://github.com/kubeflow/pipelines/issues/9803 Is there any alternative method available in KFP v2 to delete the pods after they have finished executing?

Expected result

There should be a method in KFP v2 SDK to specify the TTLStrategy inside argo workflows to have them cleaned up.

Materials and Reference

---

Impacted by this bug? Give it a 👍.

[gregsheremeta]

I'm working on this

[hbelmiro]

/assign @gregsheremeta

[papagala]

We are currently migrating all our pipelines to V2.7.0 and experienced the same problem. It was also useful to have a way to add secrets at a pipeline level and image pull secrets. Thanks @gregsheremeta 👍

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gregsheremeta]

It was also useful to have a way to add secrets at a pipeline level and image pull secrets

Extracted PipelineConfig to #11112 -- please :+1: there :)

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[juliusvonkohout]

/lifecycle frozen

[gregsheremeta]

/assign @rimolive