-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Should we increase the default certificate duration to 18 months? #8620
Comments
This issue is currently awaiting triage. If CAPI contributors determines this is a relevant issue, they will accept it by applying the The 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. |
If I see correctly this duration is only used by KCP to generate the kubeconfig secret. Today we generate it with 1 year expiry and then regenerate it after 6 months. I'm not sure how this is related with the support skew KEP. If I understand your intent correctly we should probably open this issue for kubeadm instead so the hard-coded 1 year expiry that kubeadm uses (and we just inherit) is extended. This would give us a longer expiry of the certificates on machines and thus we can keep them around for longer. |
/triage accepted Agree with @sbueringer, just adding that with automatic certificate rotation recently implemented also kubeadm expiration is not a big problem anymore |
Adding on top of that. With the current default setup (core CAPI + KCP + CABPK) we only rotate control plane machines. Worker machines don't have to be rotated as they use a self-signed server certificate that is never validated (client certificate is rotated automatically). As the skew KEP would allow us to only keep worker nodes longer extending the expiry in kubeadm is not necessary. |
note that if this is an RSA cert paired with a 2048 key, expiration > 1 year would need a bigger key. e.g. 3072. off topic cert serials must be in the 1,max range cluster-api/util/certs/types.go Line 53 in 299024f
|
I'm leaning towards closing here, giving that cert duration is driven by kubeadm and in CAPI we now have automatic certificate renewal |
@sbueringer @vincepri |
Agree, if there is still interest in seeing this implemented we need a change in kubeadm first (and thus we need an issue over there) |
Can we support configuration of |
I think the scope of this issue is the certificates on the Machines, not the kubeconfig we generate. |
I would advise avoiding to re-use the kubeconfig generated by CAPI for other services (or for users). |
Yes, sorry for responding to other questions. |
Thanks for the reply, this is very helpful to me. |
/close because:
|
@fabriziopandini: Closing this issue. In response to this:
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. |
We currently create cluster certificate that last 1 year, with the current upstream efforts to increase the support skew kubernetes/enhancements#3936, should we change the default certificate duration to allow more time for folks to upgrade their nodes?
cluster-api/util/certs/consts.go
Line 26 in 299024f
The text was updated successfully, but these errors were encountered: