In v1.15.0, kubeadm introduces the kubeadm reset phase
command with the aim of making kubeadm more modular. This modularity enables you to invoke atomic sub-steps of the reset process.
Hence, you can let kubeadm do some parts and fill in yourself where you need customizations.
kubeadm reset phase
is consistent with the kubeadm reset workflow,
and behind the scene both use the same code.
Use this command to invoke single phase of the reset workflow
Use this command to invoke single phase of the reset workflow
-h, --help help for phase
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
Using this phase you can execute preflight checks on a node that is being reset.
Run reset pre-flight checks
Run pre-flight checks for kubeadm reset.
kubeadm reset phase preflight [flags]
-f, --force Reset the node without prompting for confirmation.
-h, --help help for preflight
--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.
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
Using this phase you can remove this control-plane node from the ClusterStatus object.
Remove this node from the ClusterStatus object.
Remove this node from the ClusterStatus object if the node is a control plane node.
kubeadm reset phase update-cluster-status [flags]
-h, --help help for update-cluster-status
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
Using this phase you can remove this control-plane node’s etcd member from the etcd cluster.
Remove a local etcd member.
Remove a local etcd member for a control plane node.
kubeadm reset phase remove-etcd-member [flags]
-h, --help help for remove-etcd-member
--kubeconfig string 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. (default "/etc/kubernetes/admin.conf")
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
Using this phase you can perform cleanup on this node.
Run cleanup node.
Run cleanup node.
kubeadm reset phase cleanup-node [flags]
--cert-dir string The path to the directory where the certificates are stored. If specified, clean this directory. (default "/etc/kubernetes/pki")
--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.
-h, --help help for cleanup-node
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
kubeadm init
or kubeadm join
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.