-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 option to kubeadm upgrade command to control certificates renewal during control plane upgrade #7976
Add option to kubeadm upgrade command to control certificates renewal during control plane upgrade #7976
Conversation
… during control plane upgrade
Hi @harihud. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. |
/lgtm |
/ok-to-test |
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.
@harihud nice thanks, just in time for 2.17
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, harihud The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
… during control plane upgrade (kubernetes-sigs#7976) * Add option to kubeadm upgrade command to control certificates renewal during control plane upgrade * Remove training whitespace
… during control plane upgrade (kubernetes-sigs#7976) * Add option to kubeadm upgrade command to control certificates renewal during control plane upgrade * Remove training whitespace
Bydefault, kubeadm renews all the certificates during control plane upgrade. A deployer may want to upgrade cluster without renewing the certificates. This helps deployer while upgrading Kubernetes cluster in modular way. If something fails deployer exactly know where it is failing and so super easy to find why.
What type of PR is this?
What this PR does / why we need it: Currently kubespray does not give flexibility to deployer to control certificate renewal during control plane upgrade.
Does this PR introduce a user-facing change?: