search

kubernetes-sigs / kueue

Kubernetes-native Job Queueing
https://kueue.sigs.k8s.io
Apache License 2.0
1.28k stars 225 forks source link

Limited scope user can have a way to get overview of quota #1526

Closed panpan0000 closed 1 month ago

panpan0000 commented 7 months ago

What would you like to be added:

For people only having namespaced privilege, localqueue only shows the usage and reserved resources. but people may want to know the total usable quota , so that to plan their usage. but the total quota only exist in ClusterQueue CR , but it's cluster-scoped CRD, privilege stop people to get the total values:

Error from server (Forbidden): clusterqueues.kueue.x-k8s.io is forbidden: User "xxx" cannot list resource "clusterqueues" in API group "kueue.x-k8s.io" at the cluster scope

Why is this needed:

Completion requirements:

This enhancement requires the following artifacts:

The artifacts should be linked in subsequent comments.

kerthcet commented 6 months ago

Since it's namespaced, doesn't this already as you expected, since clusterQueue is cluster-wide. Or a namespaced user will see all the clusterQueues out of his bounds.

panpan0000 commented 6 months ago

thanks for reply, @kerthcet . But please notice that in my scenario, as a limited user, I want to get the queue QUOTA, instead of the whole ClusterQueue CR. I think it's very reasonable that for a namespaced limited user to understand how much quota still left that he/she can use.

my suggestion is to reflect the quota TOTAL in the LocalQueue CR. currently, only flavourUsage available in LocalQueue CR.

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/kueue/issues/1526#issuecomment-2155774987): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.