-
Notifications
You must be signed in to change notification settings - Fork 22
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
Comments
/sig user-experience |
Would we also consider priority at the Template level ? 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 |
Yeah exactly. This priority is specifically for the Argo controller
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. |
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)
Hum, this makes me thinks that we would also need to check if there is
something akin to pod-preemption.
Probably warrant a separate issue.
|
Suggestions:
|
/triage accepted |
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.
The text was updated successfully, but these errors were encountered: