我的书签
添加书签
移除书签kubeadm upgrade phase
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 thefollowing releases.
kubeadm upgrade node phase
Using this phase you can choose to execute the separate steps of the upgrade ofsecondary control-plane or worker nodes. Please note that kubeadm upgrade apply still has tobe called on a primary control-plane node.
Synopsis
Use this command to invoke single phase of the node workflow
Options
| -h, —help | |
| help for phase |
Options inherited from parent commands
| —rootfs string | |
| [EXPERIMENTAL] The path to the 'real' host root filesystem. |
Synopsis
Upgrade the control plane instance deployed on this node, if any
kubeadm upgrade node phase control-plane [flags]
Options
| —certificate-renewal | |
| 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 | |
| Perform the upgrade of etcd. | |
| -k, —experimental-kustomize string | |
| The path where kustomize patches for static pod manifests are stored. | |
| -h, —help | |
| help 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. |
Options inherited from parent commands
| —rootfs string | |
| [EXPERIMENTAL] The path to the 'real' host root filesystem. |
Synopsis
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]
Options
| —dry-run | |
| Do not change any state, just output the actions that would be performed. | |
| -h, —help | |
| help 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. | |
| —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 |
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 upgrade to upgrade a kubeadm node
- 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 onStack Overflow.Open an issue in the GitHub repo if you want toreport a problemorsuggest an improvement.
