-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Clarified RBAC doc about resourceNames field and create verb #50455
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
base: main
Are you sure you want to change the base?
Clarified RBAC doc about resourceNames field and create verb #50455
Conversation
Welcome @NahisWayard! |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
We try to write API verbs in lowercase boldface.
I know the RBAC page doesn't do this yet, but my suggestion is aligned to the style we'd like to see.
In my opinion, it's OK to change just this one callout even whilst the overall page still needs fixes.
Co-authored-by: Tim Bannister <[email protected]>
Co-authored-by: Tim Bannister <[email protected]>
If you restrict `list` or `watch` by resourceName, clients must include a `metadata.name` field selector in their `list` or `watch` request that matches the specified resourceName in order to be authorized. | ||
For example, `kubectl get configmaps --field-selector=metadata.name=my-configmap` | ||
You cannot restrict **deletecollection** or top-level **create** requests by resource name. | ||
For **create**, this limitation is because the name of the new object may not be known at authorization time. However, the **create** limitation applies only to top-level resources, not subresources. For example, you can use the `resourceNames` field with `pods/exec`. |
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.
We believe you can actually restrict this if you use Server side apply (SSA) for create. Could you try investigating that and updating the docs to cover that as well?
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.
(it's also OK to file a new issue about SSA / resourceNames
, and park this PR whilst that issue and detail gets addressed)
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.
I tried to apply my tests resources declared in the issue i openned. I doesn't works either
Hi @NahisWayard, thanks for this, and welcome. Since you haven’t responded to comments or feedback in 2 or more weeks, I’m closing this PR. Please feel free to reopen it when you can work on it again. /close |
@nate-double-u: Closed this PR. In response to this:
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-sigs/prow repository. |
/reopen |
@NahisWayard: Reopened this PR. In response to this:
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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Clarified interaction between RBAC rules declaring
resourceNames
and verbcreate
because the existing doc was misleadingIssue
Closes: #50454