You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases the batch admin isn't required to be in the loop when new namespaces are created. When a new namespace is created a new LQ has to be created so that users in that namespace can use Kueue quota management. As it stands this requires batch admin since the ability to create LQs more or less allows users to point to any CQ on the K8 cluster. I want the ability to be more permissive with who can create LQs while still limiting it based on spec.clusterQueue
I've created a small PoC with how I envision this working
What would you like to be added:
A way to bind CQs to users and groups
Why is this needed:
In some cases the batch admin isn't required to be in the loop when new namespaces are created. When a new namespace is created a new LQ has to be created so that users in that namespace can use Kueue quota management. As it stands this requires batch admin since the ability to create LQs more or less allows users to point to any CQ on the K8 cluster. I want the ability to be more permissive with who can create LQs while still limiting it based on
spec.clusterQueue
I've created a small PoC with how I envision this working
https://github.com/KPostOffice/kueue/tree/cq-binding
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: