-
Notifications
You must be signed in to change notification settings - Fork 64
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
feat: disabling newly added kubelet serving certificate rotation #466
Conversation
we'll need to come up with a way Karpenter can determine when it's safe to enable this flag |
will probably end up deploying the required plugin whenever karpenter is enabled to ensure this flag is safe to set, for now will keep as false until the new plugin as rolled out |
Pull Request Test Coverage Report for Build 10532706044Details
💛 - Coveralls |
one thing to also note, Karpenter will need to make sure to not pass --tls-cert-file and --tls-private-key-file as kubelet flags when this is enabled, and obviously pass --rotate-server-certificates |
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.
/test
Why do we need to do anything to preserve the current functionality? The support for |
Fixes #
Description
This PR in AgentBaker enables the kubelet flag
--rotate-server-certificates
kubelet flag. This flag will auto request and rotate the kubelet serving certificates by requesting new certs from the apiserverscertificates.k8s.io
apigroup when a certificate expiration approaches. This also requires the RotateKubeletServerCertificate feature gate to be enabled. The existing model just self signs the certificates.In terms of the karpenter impact, we are just going to stick with self signed certificates for now since we don't have everything configured to leverage this functionality.
How was this change tested?
Does this change impact docs?
Release Note