-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
kubeadm - do not generate etcd ca/certs for external etcd #63806
Conversation
Only generate the etcd CA and certificates if not configured for external etcd.
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews |
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.
Thanks for this bugfix @detiber!
I think we might wanna backport this later as well
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: detiber, luxas 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 |
Automatic merge from submit-queue (batch tested with PRs 63588, 63806). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it:
Currently we generate an etcd CA and certificates even if we are specifying an external etcd cluster when running
kubeadm init
, this PR changes this behavior to skip generating the etcd CA and certificates if configured for an external etcd cluster.Which issue(s) this PR fixes
Fixes kubernetes/kubeadm#807
Release note: