-
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
server/config: assing system:apiserver user to system:authenticated group #127902
server/config: assing system:apiserver user to system:authenticated group #127902
Conversation
/assign @deads2k |
This doesn't change the level of access. This does correct the user.Info to ensure that things like audit log rules apply as users would expect. This is a good idea to backport. /lgtm |
LGTM label has been added. Git tree hash: 9d9d1aa159c7f87874b3ccd6fda6e7659e68c5b8
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, p0lyn0mial 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 |
/triage accepted |
@p0lyn0mial does this only apply to 1.31? |
@jeremyrickard no, it doesn't. I think it applies to the previous versions as well. |
@p0lyn0mial Can you please create cherry-picks for other affected versions and link those cherry-picks here? Thanks! |
@xmudrii sure, how far back do we want to go? All the way to 1.29? |
If 1.29 is affected, yes please! |
@p0lyn0mial Approved, thanks a lot! |
…127902-upstream-release-1.29 Automated cherry pick of #127902: server/config: assing system:apiserver user to system:authenticated group
…127902-upstream-release-1.30 Automated cherry pick of #127902: server/config: assing system:apiserver user to system:authenticated group
…127902-upstream-release-1.31 Automated cherry pick of #127902: server/config: assing system:apiserver user to system:authenticated group
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: