control icon indicating copy to clipboard operation
control copied to clipboard

2.0: Deleted nodes do not go away in Kubernetes

Open eldridgeh opened this issue 7 years ago • 5 comments

Summary of Issue: After deleting nodes from the cluster details page, Kubernetes always shows the deleted nodes as NotReady

Steps to Reproduce:

  1. Spin up a cluster with multiple nodes in DO.
  2. Once the cluster is ready, manually delete a node in the control plane.
  3. ssh into the master
  4. Run kubectl get nodes

Expected Results: The deleted nodes do not show up in the cluster.

Actual Results: The deleted nodes continually show as NotReady.

Dev Info: (fill out and add links to log files)

  1. go version: 1.10
  2. SG latest commit hash or release tag: dddedff38267d34e16763fde1955ca4dec1cc5d7
  3. Number of Masters and Nodes: Any
  4. cloud provider: DO

eldridgeh avatar Nov 08 '18 22:11 eldridgeh

this option?

--min-request-timeout int     Default: 1800

An optional field indicating the minimum number of seconds a handler must keep a request open before timing it out. Currently only honored by the watch request handler, which picks a randomized value above this number as the connection timeout, to spread out load.

https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/

gopherstein avatar Nov 27 '18 22:11 gopherstein

--node-monitor-grace-period duration     Default: 40s
    Amount of time which we allow running Node to be unresponsive before marking it unhealthy. Must be N times more than kubelet's nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status.
--node-monitor-period duration     Default: 5s
    The period for syncing NodeStatus in NodeController.
--node-startup-grace-period duration     Default: 1m0s
    Amount of time which we allow starting Node to be unresponsive before marking it unhealthy.

or this....

https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/

gopherstein avatar Nov 27 '18 22:11 gopherstein

Looks like control is just removing a droplet for this step. To gracefully shut down a node it should be removed from a kubernetes cluster before.

saheienko avatar Nov 27 '18 22:11 saheienko

I think to solve this SG should send a delete node request to the kubernetes api following machine termination.

gopherstein avatar Nov 28 '18 14:11 gopherstein

Unable to test until DO remove node is fixed.

eldridgeh avatar May 01 '19 17:05 eldridgeh