-
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
✨ Remove etcd membership when doing a KubeadmControlPlane scale down #2382
✨ Remove etcd membership when doing a KubeadmControlPlane scale down #2382
Conversation
/assign @vincepri @chuckha @dlipovetsky |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: detiber 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 |
/milestone v0.3.0-rc.2 |
controlplane/kubeadm/api/v1alpha3/kubeadm_control_plane_types.go
Outdated
Show resolved
Hide resolved
6833c89
to
5822711
Compare
/hold on prereqs |
5822711
to
8c455bc
Compare
/hold cancel |
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.
To sum up these changes: the machine that is identified for deletion during scale down will have a marked for deletion label. If that same machine does not have the label indicating the etcd member has been removed, we then remove the etcd member and mark the machine as having its etcd member removed. This allows for better reentrancy during a scale down event
/lgtm
What this PR does / why we need it:
Properly removes etcd membership when doing a KubeadmControlPlane scale down
Related to #2242
Builds on #2379 #2380 #2381