Skip to content

Kueue should provide RBAC permissions for cohorts OOTB #5275

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

Open
mimowo opened this issue May 19, 2025 · 3 comments
Open

Kueue should provide RBAC permissions for cohorts OOTB #5275

mimowo opened this issue May 19, 2025 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@mimowo
Copy link
Contributor

mimowo commented May 19, 2025

What happened:

I noticed that Kueue does not provide RBAC permissions for Cohort API to update & read by admis.

What you expected to happen:

Kueue provides the RBAC natively as for other cluster-scoped resources (ClusterQueue, ResourceFlavor, Topology).

How to reproduce it (as minimally and precisely as possible):

Execute a request authenticated as a Kueue batch admin.

Anything else we need to know?:

It is not a critical bugs - administrators can easily provide the necessary RBAC, but I think we should strive for consistency, following the principle of least surprise.

See for comparison RBAC for ResourceFlavor:

https://github.com/kubernetes-sigs/kueue/blob/main/config/components/rbac/resourceflavor_editor_role.yaml

https://github.com/kubernetes-sigs/kueue/blob/main/config/components/rbac/resourceflavor_viewer_role.yaml

@mimowo mimowo added the kind/bug Categorizes issue or PR as related to a bug. label May 19, 2025
@mimowo
Copy link
Contributor Author

mimowo commented May 19, 2025

cc @gabesaba @vladikkuzn

@mimowo
Copy link
Contributor Author

mimowo commented May 19, 2025

cc @tenzen-y

@vladikkuzn
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants