Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add priority to argo workflows #2649

Open
KPostOffice opened this issue Sep 12, 2022 · 6 comments
Open

Add priority to argo workflows #2649

KPostOffice opened this issue Sep 12, 2022 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@KPostOffice
Copy link
Member

Is your feature request related to a problem? Please describe.
User requests should always be processed first. We could add the priority field to all of the workflows to influence the order which workflows are processed in.

Describe the solution you'd like

ctrl+f "priority"
https://argoproj.github.io/argo-workflows/fields/

This issue is meant to be both a proposal for priority and a place to discuss potential priorities if we decide we would like to add them.

@KPostOffice KPostOffice added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 12, 2022
@goern
Copy link
Member

goern commented Sep 14, 2022

/sig user-experience

@sesheta sesheta added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label Sep 14, 2022
@KPostOffice KPostOffice added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Sep 15, 2022
@VannTen
Copy link
Member

VannTen commented Sep 19, 2022

Would we also consider priority at the Template level ?
(This is different from pod priority for kube-scheduler right ? That would go via priorityClass, I think ?)

This is also relevant for devsecops, it could be used to have all jobs in one namespace and use one resource quota and priority (rather than multiples resource quota) for better resource utilization.

/sig devsecops

@KPostOffice
Copy link
Member Author

Would we also consider priority at the Template level ? (This is different from pod priority for kube-scheduler right ? That would go via priorityClass, I think ?)

Yeah exactly. This priority is specifically for the Argo controller

This is also relevant for devsecops, it could be used to have all jobs in one namespace and use one resource quota and priority (rather than multiples resource quota) for better resource utilization.

This is an interesting point. The only thing that I would worry about is possible starvation of lower priority tasks, I'm not sure how Argo Workflows implements priority. (Partial DOS if many user requests come at once)

Argo Workflows also allows for semaphores which can be used to limit number of parallel workflows which all require the same lock. I'm unsure how these interact with priority.

@KPostOffice KPostOffice added the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label Sep 20, 2022
@VannTen
Copy link
Member

VannTen commented Sep 21, 2022 via email

@harshad16
Copy link
Member

Suggestions:

  • Make adviser run have priority over kebechet runs

@harshad16
Copy link
Member

/triage accepted
/priority important-longterm

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 22, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
@Gkrumbach07 Gkrumbach07 moved this from 🆕 New to 📋 Backlog in Planning Board Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

5 participants