Clarify front-proxy certificate dependency on aggregation layer#55639
Open
singhvishalkr wants to merge 1 commit intokubernetes:mainfrom
Open
Clarify front-proxy certificate dependency on aggregation layer#55639singhvishalkr wants to merge 1 commit intokubernetes:mainfrom
singhvishalkr wants to merge 1 commit intokubernetes:mainfrom
Conversation
k8s-ci-robot
added
do-not-merge/invalid-commit-message
Contributor
|
[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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
added
cncf-cla: yes
The note in the kubelet certificates section described the front-proxy CA as something you only need `if you run kube-proxy to support an extension API server`. kube-proxy is the node-level Service networking component and is not involved in extension API server delivery; the actual mechanism is the apiserver aggregation layer. Reword the note to point at the aggregation layer with a link to the matching task page, while keeping the existing extension API server reference.
singhvishalkr
force-pushed
the
docs-front-proxy-aggregation-layer-clarification
branch
from
96d03b0 to
cfecffa
Compare
k8s-ci-robot
removed
the
do-not-merge/invalid-commit-message
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #55622.
The note in the "Kubelet's server and client certificates" section currently reads:
That conflates two unrelated components.
kube-proxyis the node-level Service networking dataplane and is not involved in extension API server delivery. The mechanism that actually requires the front-proxy CA is the apiserver aggregation layer, which proxies aggregated API requests on behalf of clients using the front-proxy client certificate.I rewrote the note to point at the aggregation layer task page (the same link already appears in this file at line 41 under "Optional client certificate for the front-proxy") while preserving the existing extension API server reference.
/sig docs
/kind documentation
/language en