[feature] Editing Pod's spec.

[stefanondisponibile]

Feature Area

/area sdk

What feature would you like to see?

I would like to understand what is the plan or the best practices for customizing the the Pod or container spec using kfp.
Is this feature going to be deprecated together with the rest of the v1 sdk?

What is the use case or pain point?

In my case, I'm trying to add some annotations (e.g. like it's defined here). The pain point is that I don't feel like using a deprecated feature.

Having some control over the final manifest is critical, especially in cases where you need sidecars, annotations, etc. The lack of this flexibility makes it difficult to deal with critical requirements such as secrets handling or cluster-specific customizations.

This in particular:

(PipelineTask) Replaces ContainerOp from kfp v1. Holds operations available on a task object, such as .after(), .set_memory_limit(), .enable_caching(), etc.

That etc is critical, we'll users be able to manipulate the final manifest? e.g. set_annotations?

Is there a workaround currently?

Not quite? Other than using deprecated APIs?

Related issues:

• Unable to Update annotations in component spec from pipeline parameters #4020

---

Love this idea? Give it a 👍.

[github-actions]

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.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.