volcano-sh
Support Queue‘s PriorityClassName
What would you like to be added:
Enables users to customize their queue priorities
Why is this needed:
There are some scenarios, users to customize their every job and task priorities is difficult and cumbersome. It‘s necessary to define the priority of the queue. Users can submit high-priority tasks to high-priority queues and low-priority tasks to low-priority queues. End users do not need to care about and set the priority of jobs and tasks, Of course, the priority of the job or task will still take effect.
@zbbkeepgoing queue priority is a useful ability. Would you provide a design doc or update to existing design doc firstly. I think there should be a lot of thing need to discuss. for example, the relationship between queue priority and job priority, how to avoid job starving in the low priority queue, how to use queue priority with proporiton together and other interactions.
@zbbkeepgoing queue priority is a useful ability. Would you provide a design doc or update to existing design doc firstly. I think there should be a lot of thing need to discuss. for example, the relationship between queue priority and job priority, how to avoid job starving in the low priority queue, how to use queue priority with proporiton together and other interactions.
The current idea and code are relatively simple. It seems that there are indeed many things to consider, I will write a relatively comprehensive design document first.
@zbbkeepgoing hey, since Queue is one of the basic and most improtant CRD. We'd better to take more care of the compatibility and reliability. Can you give more details of the common and original scenarios?
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
