Eric Paris Jan 2015
kubeadm upgrade node [Options]
Upgrade commands for a node in the cluster
The "node" command executes the following phases:
preflight Run upgrade node pre-flight checks control-plane Upgrade the control plane instance deployed on this node, if any kubelet-config Upgrade the kubelet configuration for this node
--certificate-renewal=true Perform the renewal of certificates used by component changed during upgrades.
--dry-run=false Do not change any state, just output the actions that would be performed.
--etcd-upgrade=true Perform the upgrade of etcd.
--experimental-patches="" Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.
--ignore-preflight-errors= A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.
--kubeconfig="/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= List of phases to be skipped
Options Inherited from Parent Commands
--azure-container-registry-config="" Path to the file containing Azure container registry configuration information.
--log-flush-frequency=5s Maximum number of seconds between log flushes
--rootfs="" [EXPERIMENTAL] The path to the 'real' host root filesystem.
--version=false Print version information and quit
January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!