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
enable kubelet server to dynamically load tls certificate files #124574
base: master
Are you sure you want to change the base?
Conversation
Welcome @zhangweikop! |
Hi @zhangweikop. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
I would suggest taking this feature to sig-auth. |
/remove-kind bug |
/triage accepted |
I would expect that logic to be re-used, not copied. |
Sorry, ignore me, I read the description without reading the code. I see that the code is re-used. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zhangweikop 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments.
This LGTM from an auth perspective.
I will defer to SIG node to determine if they are happy with the code, and if this change requires a feature gate / if that gate should be enabled or disabled by default.
What type of PR is this?
/kind bug
/kind feature
What this PR does / why we need it:
It enable kubelet tls server to watch and reload certificate files.
In our kubelet deployment, we don't use
ServerTLSBootstrap
or let kubelet to create a self-signed cert.We have other mechanism (based on internal PKI & CA) to generate and rotate the certificate files for kubelet on each host.
Therefore, we want that kubelet TLS (both client and server side) can handle the certificate update. This feature is important for us when we start generating short shorter-lived certificates for kubelet
Currently in Kubelet:
In our testing, the kubelet -> API server requests never encountered issues. The pod can be deployed and started correctly on the host after the kubelet certificate file expired and then regenerated.
Special notes for your reviewer:
certificate.Manager
so that it could be used similarly to other struct in pkg/kubelet/certificate/kubelet.go.DynamicCertKeyPairContent
struct in k8s.io/apiserver/pkg/server/dynamiccertificates.Does this PR introduce a user-facing change?