In v1.15.0, kubeadm introduced preliminary support for kubeadm upgrade node
phases.
Phases for other kubeadm upgrade
sub-commands such as apply
, could be added in the
following releases.
Using this phase you can choose to execute the separate steps of the upgrade of
secondary control-plane or worker nodes. Please note that kubeadm upgrade apply
still has to
be called on a primary control-plane node.
Use this command to invoke single phase of the node workflow
Use this command to invoke single phase of the node workflow
-h, --help help for phase
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
Upgrade the control plane instance deployed on this node, if any
Upgrade the control plane instance deployed on this node, if any
kubeadm upgrade node phase control-plane [flags]
--dry-run Do not change any state, just output the actions that would be performed.
-h, --help help for control-plane
--kubeconfig string 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. (default "/etc/kubernetes/admin.conf")
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
Upgrade the kubelet configuration for this node
Download the kubelet configuration from a ConfigMap of the form “kubelet-config-1.X” in the cluster, where X is the minor version of the kubelet. kubeadm uses the KuberneteVersion field in the kubeadm-config ConfigMap to determine what the desired kubelet version is, but the user can override this by using the –kubelet-version parameter.
kubeadm upgrade node phase kubelet-config [flags]
--dry-run Do not change any state, just output the actions that would be performed.
-h, --help help for kubelet-config
--kubeconfig string 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. (default "/etc/kubernetes/admin.conf")
--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
--rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.
kubeadm init
or kubeadm join
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.