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
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.
Synopsis
Run pre-flight checks for kubeadm reset.
kubeadm reset phase preflight [flags]
Options
| -f, --force | |
| Reset the node without prompting for confirmation. | |
| -h, --help | |
| help for preflight | |
| --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. | |
Options inherited from parent commands
| --rootfs string | |
| [EXPERIMENTAL] The path to the 'real' host root filesystem. | |
kubeadm reset phase update-cluster-status
Using this phase you can remove this control-plane node from the ClusterStatus object.
Synopsis
Remove this node from the ClusterStatus object if the node is a control plane node.
kubeadm reset phase update-cluster-status [flags]
Options
| -h, --help | |
| help for update-cluster-status | |
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.
Synopsis
Remove a local etcd member for a control plane node.
kubeadm reset phase remove-etcd-member [flags]
Options
| -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.
Synopsis
Run cleanup node.
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. | |
| --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 | |
Options inherited from parent commands
| --rootfs string | |
| [EXPERIMENTAL] The path to the 'real' host root filesystem. | |
What’s next
- kubeadm init to bootstrap a Kubernetes control-plane node
- kubeadm join to connect a node to the cluster
- kubeadm reset to revert any changes made to this host by
kubeadm initorkubeadm join - kubeadm alpha to try experimental functionality
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.
Page last modified on September 07, 2019 at 1:35 AM PST by
kubeadm: update reference documentation for 1.16 (#16014) (Page History)