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

—rootfs string
	[EXPERIMENTAL] The path to the ‘real’ host root filesystem.

kubeadm reset phase preflight

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.

-f, —force
	Reset the node without prompting for confirmation.
-h, —help

—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.

Using this phase you can remove this control-plane node from the ClusterStatus object.

Remove this node from the ClusterStatus object (DEPRECATED).

Remove this node from the ClusterStatus object (DEPRECATED).

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

—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.

—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.
-h, —help
	help for cleanup-node