-
Notifications
You must be signed in to change notification settings - Fork 879
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
Add a tool script for updating the certificates and private keys #2400
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: lfbear <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
So glad that see you back @lfbear :) |
Cool, I think this feature also need to be realized in |
@chaosi-zju Please look at this. I'm so sorry for missing this. Nowadays, a lot of users want a tools to update their certificates. |
ok, I am interested in this PR too, review is on going. But before I give any comments, I would like to spend some time investigating the official practice of k8s certificate rotation. since this is a key feature, we will strive to make it the best. |
Make sense. |
I hope this could be done along with karmada-io/community#69. |
Signed-off-by: lfbear [email protected]
What type of PR is this?
generate_cert_secret
toutil.sh
What this PR does / why we need it:
For early users, the expiration date of certificates and private keys was only one year. The expiration of the cert will lead to an unavailable status for some components, such as Etcd.
This script will re-sign all certs and keys and update the related secrets in Karmada's host cluster. It will also update the credentials in Karmada's kubeconfig file.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: