This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
secure communciation from kubernetes API to kubelet API endpoint #1978
Conversation
This file contains 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
|
@pidah Thanks!
|
ghost
assigned
|
@pidah nevermind I gofmt'd myself, gonna run E2E now |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What this PR does / why we need it:
Communication from kubelet -> API server is currently secure, but not API server -> kubelet. The kubelet exposes an unauthenticated endpoint on port 10250 which can be exploited from any other node on the cluster.
This PR adds:
More info is available here:
https://kubernetes.io/docs/admin/kubelet-authentication-authorization/
https://kubernetes.io/docs/tasks/administer-cluster/securing-a-cluster/
kubernetes/kubernetes#52184