Skip to content

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

stlaz
Copy link
Member

@stlaz stlaz commented Jul 23, 2025

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 headers
are 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?

Standard Kubernetes HTTP headers for communication to the aggregated API servers are now always added to the `kube-system/extension-apiserver-authentication` config map.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/cc enj liggitt

@k8s-ci-robot k8s-ci-robot requested review from enj and liggitt July 23, 2025 11:10
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jul 23, 2025
@stlaz
Copy link
Member Author

stlaz commented Jul 23, 2025

/sig auth

@k8s-ci-robot k8s-ci-robot added the sig/auth Categorizes an issue or PR as relevant to SIG Auth. label Jul 23, 2025
@stlaz
Copy link
Member Author

stlaz commented Jul 23, 2025

/hold
Looks like there is a bug.

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.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 23, 2025
@enj enj moved this to Needs Triage in SIG Auth Jul 23, 2025
stlaz added 2 commits July 24, 2025 13:15
…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]>
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stlaz
Once this PR has been reviewed and has the lgtm label, please assign mikedanese for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Jul 24, 2025
@micahhausler
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 28, 2025
@micahhausler micahhausler moved this from Needs Triage to Backlog in SIG Auth Jul 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/apiserver area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: Backlog
Development

Successfully merging this pull request may close these issues.

Default standard request headers for aggregation
3 participants