[Core feature] Allow setting concurrency policy for launch plans with schedule.

[debajyoti-truefoundry]

Motivation: Why do you think this is important?

It will be nice to set a concurrency policy when creating a launch plan with a schedule. I have added relevant documentation from K8s CronJobs.

https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#concurrency-policy
https://argo-workflows.readthedocs.io/en/latest/fields/#cronworkflowspec (Please check the concurrencyPolicy field.)

Goal: What should the final outcome look like, ideally?

I can set Allow, Forbid or Replace as concurrency policy for launch plans with a schedule.

Describe alternatives you've considered

None.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[dosubot]

🤖

It seems like you've got this under control, if you want help or have specific questions, let me know what I can do for you!

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[debajyoti-truefoundry]

I just found another issue discussing the same feature. Feel free to close this issue if the projecting tracks this feature there.

#267 (comment)

[eapolinario]

An idea similar to this is actually being discussed in #3754. Please, engage there so that we can prioritize this accordingly.