Synopsis
Upgrade commands for a node in the cluster
The “node” command executes the following phases:
control-plane Upgrade the control plane instance deployed on this node, if any
kubelet-config Upgrade the kubelet configuration for this node
kubeadm upgrade node [flags]
Options
| --certificate-renewal Default: true | |
| Perform the renewal of certificates used by component changed during upgrades. | |
| --dry-run | |
| Do not change any state, just output the actions that would be performed. | |
| --etcd-upgrade Default: true | |
| Perform the upgrade of etcd. | |
| -k, --experimental-kustomize string | |
| The path where kustomize patches for static pod manifests are stored. | |
| -h, --help | |
| help for node | |
| --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. | |
| --kubelet-version string | |
| The *desired* version for the kubelet config after the upgrade. If not specified, the KubernetesVersion from the kubeadm-config ConfigMap will be used | |
| --skip-phases stringSlice | |
| List of phases to be skipped | |
Options inherited from parent commands
| --rootfs string | |
| [EXPERIMENTAL] The path to the 'real' host root filesystem. | |
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 January 03, 2020 at 12:39 PM PST by
regenerate ref docs, 1.17, script chgs (#18067) (Page History)