mirror of https://github.com/k3s-io/k3s
5826b09a19
Automatic merge from submit-queue (batch tested with PRs 43018, 42713) kubeadm: Don't drain and remove the current node on kubeadm reset **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: In v1.5, `kubeadm reset` would drain your node and remove it from your cluster if you specified, but now in v1.6 we can't do that due to the RBAC rules we have set up. After conversations with @liggitt, I also agree this functionality was somehow a little mis-placed (though still very convenient to use), so we're removing it for v1.6. It's the system administrator's duty to drain and remove nodes from the cluster, not the nodes' responsibility. The current behavior is therefore a bug that needs to be fixed in v1.6 **Release note**: ```release-note kubeadm: `kubeadm reset` won't drain and remove the current node anymore ``` @liggitt @deads2k @jbeda @dmmcquay @pires @errordeveloper |
||
|---|---|---|
| .. | ||
| clicheck | ||
| cloud-controller-manager | ||
| gendocs | ||
| genkubedocs | ||
| genman | ||
| genslateyaml | ||
| genswaggertypedocs | ||
| genutils | ||
| genyaml | ||
| gke-certificates-controller | ||
| hyperkube | ||
| kube-apiserver | ||
| kube-controller-manager | ||
| kube-proxy | ||
| kubeadm | ||
| kubectl | ||
| kubelet | ||
| kubemark | ||
| libs/go2idl | ||
| linkcheck | ||
| mungedocs | ||
| BUILD | ||
| OWNERS | ||