Performs a best effort revert of changes made by kubeadm init
or kubeadm join
.
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:
preflight Run reset pre-flight checks
remove-etcd-member Remove a local etcd member.
cleanup-node Run cleanup node.
kubeadm reset [flags]
--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 | |
Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket. | |
-f, --force | |
Reset the node without prompting for confirmation. | |
-h, --help | |
help for reset | |
--ignore-preflight-errors strings | |
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 can be searched for an existing kubeconfig file. | |
--skip-phases strings | |
List of phases to be skipped |
--rootfs string | |
[EXPERIMENTAL] The path to the 'real' host root filesystem. |
kubeadm reset
is responsible for cleaning up a node local file system from files that were created using the kubeadm init
or kubeadm join
commands. For control-plane nodes reset
also removes the local stacked etcd member of this node from the etcd cluster.
kubeadm reset phase
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.
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.
© 2022 The Kubernetes Authors
Documentation Distributed under CC BY 4.0.
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-reset/