-
Notifications
You must be signed in to change notification settings - Fork 40k
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
add local subject access review API #32407
Conversation
Create(sar *authorizationapi.LocalSubjectAccessReview) (result *authorizationapi.LocalSubjectAccessReview, err error) | ||
} | ||
|
||
func (c *localSubjectAccessReviews) Create(sar *authorizationapi.LocalSubjectAccessReview) (result *authorizationapi.LocalSubjectAccessReview, err error) { |
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.
you'll need to manually create this for the fake generated client as well, right?
surprised there were no doc changes for the endpoint. do we need to hook up api doc generation for this api group? |
oh, no :)
|
Eh, assume I fix up the quibbling generators. |
LGTM, modulo fake client method and generated bits |
336d6ab
to
b2abdc8
Compare
Junit didn't report |
@deads2k |
b2abdc8
to
356f890
Compare
356f890
to
e5dbfda
Compare
GCE e2e build/test passed for commit e5dbfda. |
Automatic merge from submit-queue |
Automatic merge from submit-queue Run hack/update-codegen.sh in release-1.4 for generating an updated 1.4 clientset @caesarxuchao doing steps 1 and 2 as described here #33851 (comment) adds apps, authentication, certificates, rbac, and storage. The reason there are substantial deletions (aside from the oneliner "this package is generated by client-gen with arguments...") is because PR #32407 added a resource to the 1.4 clientset even though the resource is not present in 1.4 and the PR is targeted to 1.5. So this corrects that, as a bonus.
Adds a local subject access review endpoint to allow a project-admin (someone with full rights within a namespace) the power to inspect whether a person can perform an action in his namespace. This is a separate resource be factoring like this ensures that it is impossible for him to look outside his namespace and makes it possible to create authorization rules that can restrict this power to a project-admin in his own namespace. Other factorings require introspection of objects.
@kubernetes/sig-auth
This change is