kubeadm reset

This command reverts any changes made by kubeadm init or kubeadm join.

What's next

Run this to revert any changes made to this host by ‘kubeadm init’ or ‘kubeadm join’.

Synopsis

Run this to revert any changes made to this host by ‘kubeadm init’ or ‘kubeadm join’.

kubeadm reset [flags]

Options

--cert-dir string Default: "/etc/kubernetes/pki"
	The path to the directory where the certificates are stored. If specified, clean this directory.
--cri-socket string Default: "/var/run/dockershim.sock"
	The path to the CRI socket to use with crictl when cleaning up containers.
-f, --force
	Reset the node without prompting for confirmation.
-h, --help
	help for reset
--ignore-preflight-errors stringSlice
	A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
--kubeconfig string Default: "/etc/kubernetes/admin.conf"
	The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations are searched for an existing KubeConfig file.

Options inherited from parent commands

--rootfs string
	[EXPERIMENTAL] The path to the 'real' host root filesystem.

External etcd clean up!

kubeadm reset 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.

To wipe etcd data it is recommended you use a client like etcdctl, such as:

etcdctl del "" --prefix

See the etcd documentation for more information.

What's next

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

Feedback

Was this page helpful?

Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

Reference