-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Mention the builtin clusterrole in kubelet authorization #50145
base: main
Are you sure you want to change the base?
Conversation
[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 |
✅ Pull request preview available for checking
To edit notification comments on pull requests, go to your Netlify site configuration. |
Enabling this gate also ensure that the builtin `system:kubelet-api-admin` ClusterRole | ||
is updated with permissions to access all the above mentioned subresources. |
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 should caveat this that it applies to clusters using RBAC mode authz.
(Clusters not using RBAC don't have ClusterRoles).
This PR updates the description about the kubelet fine-grained API authorization.
This PR updates the description about the kubelet fine-grained API authorization.
According to the upstream implementation (kubernetes/kubernetes#126347), the fine-grained authorization doesn't include
nodes/spec
.The previous docs didn't mention that the builtin clusterrole exists and will get updated.