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
Fix RBAC to visibility into Local Queues #1412
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @PBundyra. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
/lgtm |
LGTM label has been added. Git tree hash: 1f261b6100ff8332394a7b496c176efe2c43d7b1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you remove an empty line in the release note?
/approve
/release-note-edit
RBAC to visibility into Local Queues is fixed
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: PBundyra, tenzen-y The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/release-note-edit
|
Due to #1372 /test pull-kueue-test-e2e-main-1-27 |
/release-note-edit
it was an unreleased feature |
What type of PR is this?
/kind bug
What this PR does / why we need it:
It fixes RBAC so users with
kueue-batch-user-role
have access to pending workloads in namespaces they are bound to. Before that admins needed to create a separateRole
for each namespace.Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?