Skip to content
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

Closed
boluisa opened this issue Mar 23, 2020 · 9 comments
Closed

improve safety for end-user during control plane deletion #2759

boluisa opened this issue Mar 23, 2020 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@boluisa
Copy link

boluisa commented Mar 23, 2020

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

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 23, 2020
@vincepri
Copy link
Member

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?

@vincepri
Copy link
Member

/priority awaiting-more-evidence

@k8s-ci-robot k8s-ci-robot added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Mar 23, 2020
@boluisa
Copy link
Author

boluisa commented Mar 24, 2020

@vincepri no, not via scaling down. I meant by deleting the control plane object itself. for example: kubectl delete machine controlplane-1

@detiber
Copy link
Member

detiber commented Mar 24, 2020

One way to achieve this:

  • Add a KCP owned finalizer to the Machine when creating or adopting
  • Update etcd/kubeadm config entries when deletion of Machine is detected before removing finalizer

@vincepri vincepri removed the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Mar 24, 2020
@vincepri
Copy link
Member

/milestone Next

gonna punt to next for now given the pending testing and robustness in KCP #2753

@k8s-ci-robot k8s-ci-robot added this to the Next milestone Mar 24, 2020
@vincepri
Copy link
Member

Somewhat related: #2818

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 29, 2020
@vincepri
Copy link
Member

Closing this given that we reconcile the etcd membership with what Machines are available (and without a deletion timestamp).

/close

@k8s-ci-robot
Copy link
Contributor

@vincepri: Closing this issue.

In response to this:

Closing this given that we reconcile the etcd membership with what Machines are available (and without a deletion timestamp).

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants