# kubeadm upgrade phases

kubeadm upgrade phaseskubeadm upgrade apply phaseUsing the phases of kubeadm upgrade apply, you can choose to execute the separate steps of the initial upgrade of a control plane node.SynopsisUse this command to invoke single phase of the "apply" workflowkubeadm upgrade apply phase [flags] Options-h, --helphelp for phaseOptions inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisRun preflight checks before upgradekubeadm upgrade apply phase preflight [flags] Options--allow-experimental-upgradesShow unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes.--allow-release-candidate-upgradesShow release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes.--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output what actions would be performed.-f, --forceForce upgrading although some requirements might not be met. This also implies non-interactive mode.-h, --helphelp for preflight--ignore-preflight-errors stringsA list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks.--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.-y, --yesPerform the upgrade and do not prompt for confirmation (non-interactive mode).Options inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpgrade the control planekubeadm upgrade apply phase control-plane [flags] Options--certificate-renewal Default: truePerform the renewal of certificates used by component changed during upgrades.--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output what actions would be performed.--etcd-upgrade Default: truePerform the upgrade of etcd.-h, --helphelp for control-plane--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.--patches stringPath to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment". "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.Options inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpload the kubeadm and kubelet configurations to ConfigMapskubeadm upgrade apply phase upload-config [flags] Options-h, --helphelp for upload-configOptions inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpgrade the kubelet configuration for this node by downloading it from the kubelet-config ConfigMap stored in the clusterkubeadm upgrade apply phase kubelet-config [flags] Options--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output what actions would be performed.-h, --helphelp for kubelet-config--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.--patches stringPath to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment". "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.Options inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisConfigures bootstrap token and cluster-info RBAC ruleskubeadm upgrade apply phase bootstrap-token [flags] Options--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output what actions would be performed.-h, --helphelp for bootstrap-token--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 stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpgrade the default kubeadm addonskubeadm upgrade apply phase addon [flags] Options-h, --helphelp for addonOptions inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisRun post upgrade taskskubeadm upgrade apply phase post-upgrade [flags] Options--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output what actions would be performed.-h, --helphelp for post-upgrade--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 stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.kubeadm upgrade node phaseUsing the phases of kubeadm upgrade node you can choose to execute the separate steps of the upgrade of secondary control-plane or worker nodes.SynopsisUse this command to invoke single phase of the "node" workflowkubeadm upgrade node phase [flags] Options-h, --helphelp for phaseOptions inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.Run upgrade node pre-flight checksSynopsisRun pre-flight checks for kubeadm upgrade node.kubeadm upgrade node phase preflight [flags] Options--config stringPath to a kubeadm configuration file.-h, --helphelp for preflight--ignore-preflight-errors stringsA 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 stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpgrade the control plane instance deployed on this node, if anykubeadm upgrade node phase control-plane [flags] Options--certificate-renewal Default: truePerform the renewal of certificates used by component changed during upgrades.--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output the actions that would be performed.--etcd-upgrade Default: truePerform the upgrade of etcd.-h, --helphelp for control-plane--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.--patches stringPath to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment". "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.Options inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpgrade the kubelet configuration for this node by downloading it from the kubelet-config ConfigMap stored in the clusterkubeadm upgrade node phase kubelet-config [flags] Options--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output the actions that would be performed.-h, --helphelp for kubelet-config--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.--patches stringPath to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment". "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.Options inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisUpgrade the default kubeadm addonskubeadm upgrade node phase addon [flags] Options-h, --helphelp for addonOptions inherited from parent commands--rootfs stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.SynopsisRun post upgrade taskskubeadm upgrade node phase post-upgrade [flags] Options--config stringPath to a kubeadm configuration file.--dry-runDo not change any state, just output the actions that would be performed.-h, --helphelp for post-upgrade--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 stringThe path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.What's nextkubeadm init to bootstrap a Kubernetes control-plane nodekubeadm join to connect a node to the clusterkubeadm reset to revert any changes made to this host by kubeadm init or kubeadm joinkubeadm upgrade to upgrade a kubeadm nodekubeadm alpha to try experimental functionality