-
Notifications
You must be signed in to change notification settings - Fork 41k
apiserver trust-controller: always include default RequestHeaders in the trust CM #133142
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: master
Are you sure you want to change the base?
Conversation
/sig auth |
/hold My guess is merging two different headers with different case will turn into both appearing in the CM, which results in doubled groups/extras in the authenticated UserInfos. |
…the trust CM These standard headers are required for the aggregator to work correctly. Always include them in the cluster's trust config map. Signed-off-by: Stanislav Láznička <[email protected]>
Signed-off-by: Stanislav Láznička <[email protected]>
3d545df
to
b972d64
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stlaz 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 |
/triage accepted |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds the standard Kubernetes headers for authentication with remote headers to the
kube-system/extension-apiserver-authentication
config map of every cluster. These headersare used to relay user information from the kube-apiserver to the aggregated API servers and
so they should always be present in the authentication discovery that's based off of this CM.
Which issue(s) this PR is related to:
Fixes #126821
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc enj liggitt