-
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
improve safety for end-user during control plane deletion #2759
Comments
The current code in v1alpha3 takes care of this when scaling down https://github.com/kubernetes-sigs/cluster-api/blob/master/controlplane/kubeadm/controllers/kubeadm_control_plane_controller.go#L541-L550, is this what you were asking? |
/priority awaiting-more-evidence |
@vincepri no, not via scaling down. I meant by deleting the control plane object itself. for example: |
One way to achieve this:
|
/milestone Next gonna punt to next for now given the pending testing and robustness in KCP #2753 |
Somewhat related: #2818 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Closing this given that we reconcile the etcd membership with what Machines are available (and without a deletion timestamp). /close |
@vincepri: 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. |
User Story
As an operator, I would like to delete control plane nodes in a way that does not leave behind etcd members or in a way that does not require running Kubeadm reset prior to machine deletion.
Detailed Description
A delete of a control plane object should remove it corresponding etcd member from the etcd cluster.
/kind feature
The text was updated successfully, but these errors were encountered: