kubeadm reset phase

kubeadm reset phase enables you to invoke atomic steps of the node reset process. Hence, you can let kubeadm do some of the work and you can fill in the gaps if you wish to apply customization.

kubeadm reset phase is consistent with the kubeadm reset workflow, and behind the scene both use the same code.

kubeadm reset phase

Use this command to invoke single phase of the reset workflow

Synopsis

Use this command to invoke single phase of the reset workflow

Options

-h, —help

help for phase

Options inherited from parent commands

—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

Synopsis

Run pre-flight checks for kubeadm reset.

  1. kubeadm reset phase preflight [flags]

Options

—dry-run

Don’t apply any changes; just output what would be done.

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

Options inherited from parent commands

—rootfs string

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

kubeadm reset phase remove-etcd-member

Using this phase you can remove this control-plane node’s etcd member from the etcd cluster.

Remove a local etcd member.

Synopsis

Remove a local etcd member for a control plane node.

  1. kubeadm reset phase remove-etcd-member [flags]

Options

—dry-run

Don’t apply any changes; just output what would be done.

-h, —help

help for remove-etcd-member

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

Options inherited from parent commands

—rootfs string

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

kubeadm reset phase cleanup-node

Using this phase you can perform cleanup on this node.

Run cleanup node.

Synopsis

Run cleanup node.

  1. kubeadm reset phase cleanup-node [flags]

Options

—cert-dir string     Default: “/etc/kubernetes/pki”

The path to the directory where the certificates are stored. If specified, clean this directory.

—cleanup-tmp-dir

Cleanup the “/etc/kubernetes/tmp” 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.

—dry-run

Don’t apply any changes; just output what would be done.

-h, —help

help for cleanup-node

Options inherited from parent commands

—rootfs string

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

What’s next