-
Notifications
You must be signed in to change notification settings - Fork 262
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
Expose Flavors in LocalQueue Status #3122
Comments
Updating the flavors in status will eat QPS to update the information which is just one step away so I would prefer to understand what is the use-case. Would it work for you composing these queries: CQ_NAME=$(kubectl get lq/user-queue -ojson | jq -r .spec.clusterQueue)
kubectl get cq/$CQ_NAME -ojson | jq .spec.resourceGroups\[\].flavors\[\].name If this works, maybe just need a docs update for "common tasks", or extend kueuectl? |
We already have API calls to populate the usage, so this wouldn't add additional calls.
This might not work, depending on the RBAC rules, as users might not have read access to ClusterQueues. |
I see, sounds good |
The RBAC permission deeply depends on the organization's policies. So, it might be better to add troubleshooting guide or any dedicated task document how to obtain the tied resourceFlavors. |
This is exactly the issue we are facing. Letting the users know the flavors is useful since it can give an idea of the capabilities provided by a LocalQueue. (i.e. one flavor may have newer GPUs) |
/assign |
What would you like to be added:
Add a status field to LocalQueue which lists out available flavors
Why is this needed:
I would like to be able to see the resource flavors available in each LocalQueue that I have access to
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: