We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To prevent users from hijacking a Capacity by creating multiple Queues, we should have a single heap for a Capacity (spin off from #80 (comment))
/kind feature
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
/retitle Introduce a single heap for per ClusterQueue
Maybe I am confused but after this issue is closed, what is left for kueue.queue to hold?
is just a pointer to ClusterQueue , now that the head moved from Queue to Cluster Queue I don't see a point on having a Queue controller
#80 (comment)
alculquicondor
Successfully merging a pull request may close this issue.
To prevent users from hijacking a Capacity by creating multiple Queues, we should have a single heap for a Capacity (spin off from #80 (comment))
/kind feature
The text was updated successfully, but these errors were encountered: