kubeadm reset

Performs a best effort revert of changes made to this host by ‘kubeadm init’ or ‘kubeadm join’

Performs a best effort revert of changes made to this host by ‘kubeadm init’ or ‘kubeadm join’

The “reset” command executes the following phases:

kubeadm reset is responsible for cleaning up a node local file system from files that were created using the kubeadm init or commands. For control-plane nodes reset also removes the local stacked etcd member of this node from the etcd cluster and also removes this node’s information from the kubeadm ClusterStatus object. ClusterStatus is a kubeadm managed Kubernetes API object that holds a list of kube-apiserver endpoints.

can be used to execute the separate phases of the above workflow. To skip a list of phases you can use the --skip-phases flag, which works in a similar way to the kubeadm join and kubeadm init phase runners.

will not delete any etcd data if external etcd is used. This means that if you run kubeadm init again using the same etcd endpoints, you will see state from previous clusters.

See the etcd documentation for more information.

• to bootstrap a Kubernetes control-plane node
• kubeadm join to bootstrap a Kubernetes worker node and join it to the cluster