Support Argo/Tekton workflows

kubernetes-sigs / kueue

Kubernetes-native Job Queueing

https://kueue.sigs.k8s.io

Apache License 2.0

1.46k stars 262 forks source link

Support Argo/Tekton workflows #74

Open ahg-g opened 2 years ago

ahg-g commented 2 years ago

This is lower priority than https://github.com/kubernetes-sigs/kueue/issues/65, but it would be good to have an integration with a workflow framework.

Argo supports the suspend flag, the tricky part is that suspend is for the whole workflow, meaning a QueuedWorkload would need to represent the resources of the whole workflow all at once.

Ideally Argo should create jobs per sequential step, and then resource reservation happens one step at a time.

terrytangyuan commented 2 months ago

Can someone remove "Tekton" from the title of this issue?

alculquicondor commented 2 months ago

Ideally, the mechanism should be extensible to Tekton and any other workflow manager. But certainly, we can start with just Argo.

kerthcet commented 2 months ago

Ideally, the mechanism should be extensible to Tekton and any other workflow manager. But certainly, we can start with just Argo.

+1 this should be aligned with other workflow tools as well, from kueue side.

KunWuLuan commented 2 months ago

Ideally, the mechanism should be extensible to Tekton and any other workflow manager. But certainly, we can start with just Argo.

I understand. In that case, this component should aim to minimize its dependencies on modifications to other workflow managers.

alculquicondor commented 2 months ago

Not necessarily. But it should aim at modification that could be feasible in other projects. Just like we did the suspend field for Job that could be replicated in projects such as kubeflow and kuberay.

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

KunWuLuan commented 1 month ago

/remove-lifecycle rotten