This repository has been archived by the owner on Jul 30, 2021. It is now read-only.
cmd/checkpoint: use kubelet's client certs for the kubelet API #348
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
Use the client certs in the kubelet's kubeconfig to talk to the kubelet API. This has on effect currently, but will once the kubelet enables API auth. We assume the kubelet's client certs originate from the same CA that cert auth trusts.
k8s-ci-robot
added
the
cncf-cla: yes
|
rktbot run checkpointer tests |
|
@pbx0 all green! |
peebs
approved these changes
Mar 3, 2017
5 tasks
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.
Use the client certs in the kubelet's kubeconfig to talk to the
kubelet API. This has no effect currently, but will once the
kubelet enables API auth. We assume the kubelet's client certs
originate from the same CA that cert auth trusts.
These are checkpointer changes split out from #345 so we can
do a release then import it later once we turn on kubelet auth.
cc @pbx0