- 1:
- 2:
- 3:
- 4:
- 5:
- 6:
- 7:
- 8:
- 9:
- 10:
- 11:
- 12:
- 13:
- 14:
- 15:
- 16:
- 17:
- 18:
- 19:
- 20:
- 21:
- 22:
- 23:
- 24:
- 25:
- 26:
- 27:
Upgrade your cluster smoothly to a newer version with this command
Synopsis
Upgrade your cluster smoothly to a newer version with this command
kubeadm upgrade [flags]
Options
-h, --help |
| help for upgrade |
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
1 -
Upgrade your Kubernetes cluster to the specified version
Synopsis
Upgrade your Kubernetes cluster to the specified version
The "apply [version]" command executes the following phases:
preflight Run preflight checks before upgrade
control-plane Upgrade the control plane
upload-config Upload the kubeadm and kubelet configurations to ConfigMaps
/kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
/kubelet Upload the kubelet configuration to a ConfigMap
kubelet-config Upgrade the kubelet configuration for this node
bootstrap-token Configures bootstrap token and cluster-info RBAC rules
addon Upgrade the default kubeadm addons
/coredns Upgrade the CoreDNS addon
/kube-proxy Upgrade the kube-proxy addon
post-upgrade Run post upgrade tasks
kubeadm upgrade apply [version]
Options
--allow-experimental-upgrades |
| Show unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes. |
--allow-release-candidate-upgrades |
| Show release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes. |
--certificate-renewal Default: true |
| Perform the renewal of certificates used by component changed during upgrades. |
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
--etcd-upgrade Default: true |
| Perform the upgrade of etcd. |
-f, --force |
| Force upgrading although some requirements might not be met. This also implies non-interactive mode. |
-h, --help |
| help for apply |
--ignore-preflight-errors strings |
| A 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. |
--patches string |
| Path 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. |
--print-config |
| Specifies whether the configuration file that will be used in the upgrade should be printed or not. |
--skip-phases strings |
| List of phases to be skipped |
-y, --yes |
| Perform the upgrade and do not prompt for confirmation (non-interactive mode). |
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
2 -
Use this command to invoke single phase of the "apply" workflow
Synopsis
Use this command to invoke single phase of the "apply" workflow
kubeadm upgrade apply phase [flags]
Options
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
3 -
Upgrade the default kubeadm addons
Synopsis
Upgrade the default kubeadm addons
kubeadm upgrade apply phase addon [flags]
Options
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
4 -
Upgrade all the addons
Synopsis
Upgrade all the addons
kubeadm upgrade apply phase addon all [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help for all |
--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 string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
5 -
Upgrade the CoreDNS addon
Synopsis
Upgrade the CoreDNS addon
kubeadm upgrade apply phase addon coredns [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help for coredns |
--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 string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
6 -
Upgrade the kube-proxy addon
Synopsis
Upgrade the kube-proxy addon
kubeadm upgrade apply phase addon kube-proxy [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help for kube-proxy |
--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 |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
7 -
Configures bootstrap token and cluster-info RBAC rules
Synopsis
Configures bootstrap token and cluster-info RBAC rules
kubeadm upgrade apply phase bootstrap-token [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
8 -
Upgrade the control plane
Synopsis
Upgrade the control plane
kubeadm upgrade apply phase control-plane [flags]
Options
--certificate-renewal Default: true |
| Perform the renewal of certificates used by component changed during upgrades. |
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
--etcd-upgrade Default: true |
| Perform the upgrade of etcd. |
-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. |
--patches string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
9 -
Upgrade the kubelet configuration for this node
Synopsis
Upgrade the kubelet configuration for this node by downloading it from the kubelet-config ConfigMap stored in the cluster
kubeadm upgrade apply phase kubelet-config [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions 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. |
--patches string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
10 -
Run post upgrade tasks
Synopsis
Run post upgrade tasks
kubeadm upgrade apply phase post-upgrade [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
11 -
Run preflight checks before upgrade
Synopsis
Run preflight checks before upgrade
kubeadm upgrade apply phase preflight [flags]
Options
--allow-experimental-upgrades |
| Show unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes. |
--allow-release-candidate-upgrades |
| Show release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes. |
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-f, --force |
| Force upgrading although some requirements might not be met. This also implies non-interactive mode. |
-h, --help |
| help for preflight |
--ignore-preflight-errors strings |
| A 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, --yes |
| Perform the upgrade and do not prompt for confirmation (non-interactive mode). |
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
12 -
Upload the kubeadm and kubelet configurations to ConfigMaps
Synopsis
Upload the kubeadm and kubelet configurations to ConfigMaps
kubeadm upgrade apply phase upload-config [flags]
Options
-h, --help |
| help for upload-config |
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
13 -
Upload all the configurations to ConfigMaps
Synopsis
Upload all the configurations to ConfigMaps
kubeadm upgrade apply phase upload-config all [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help for all |
--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 |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
14 -
Upload the kubeadm ClusterConfiguration to a ConfigMap
Synopsis
Upload the kubeadm ClusterConfiguration to a ConfigMap
kubeadm upgrade apply phase upload-config kubeadm [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help for kubeadm |
--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 |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
15 -
Upload the kubelet configuration to a ConfigMap
Synopsis
Upload the kubelet configuration to a ConfigMap
kubeadm upgrade apply phase upload-config kubelet [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output what actions would be performed. |
-h, --help |
| help for kubelet |
--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 |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
16 -
Show what differences would be applied to existing static pod manifests. See also: kubeadm upgrade apply --dry-run
Synopsis
Show what differences would be applied to existing static pod manifests. See also: kubeadm upgrade apply --dry-run
kubeadm upgrade diff [version] [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
-c, --context-lines int Default: 3 |
| How many lines of context in the diff |
-h, --help |
| help for diff |
--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 |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
17 -
Upgrade commands for a node in the cluster
Synopsis
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
addon Upgrade the default kubeadm addons
/coredns Upgrade the CoreDNS addon
/kube-proxy Upgrade the kube-proxy addon
post-upgrade Run post upgrade tasks
kubeadm upgrade node [flags]
Options
--certificate-renewal Default: true |
| Perform the renewal of certificates used by component changed during upgrades. |
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output the actions that would be performed. |
--etcd-upgrade Default: true |
| Perform the upgrade of etcd. |
-h, --help |
| help for node |
--ignore-preflight-errors strings |
| A 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. |
--patches string |
| Path 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. |
--skip-phases strings |
| List of phases to be skipped |
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
18 -
Use this command to invoke single phase of the "node" workflow
Synopsis
Use this command to invoke single phase of the "node" workflow
kubeadm upgrade node phase [flags]
Options
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
19 -
Upgrade the default kubeadm addons
Synopsis
Upgrade the default kubeadm addons
kubeadm upgrade node phase addon [flags]
Options
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
20 -
Upgrade all the addons
Synopsis
Upgrade all the addons
kubeadm upgrade node phase addon all [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output the actions that would be performed. |
-h, --help |
| help for all |
--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 string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
21 -
Upgrade the CoreDNS addon
Synopsis
Upgrade the CoreDNS addon
kubeadm upgrade node phase addon coredns [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output the actions that would be performed. |
-h, --help |
| help for coredns |
--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 string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
22 -
Upgrade the kube-proxy addon
Synopsis
Upgrade the kube-proxy addon
kubeadm upgrade node phase addon kube-proxy [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output the actions that would be performed. |
-h, --help |
| help for kube-proxy |
--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 |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
23 -
Upgrade the control plane instance deployed on this node, if any
Synopsis
Upgrade the control plane instance deployed on this node, if any
kubeadm upgrade node phase control-plane [flags]
Options
--certificate-renewal Default: true |
| Perform the renewal of certificates used by component changed during upgrades. |
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output the actions that would be performed. |
--etcd-upgrade Default: true |
| Perform the upgrade of etcd. |
-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. |
--patches string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
24 -
Upgrade the kubelet configuration for this node
Synopsis
Upgrade the kubelet configuration for this node by downloading it from the kubelet-config ConfigMap stored in the cluster
kubeadm upgrade node phase kubelet-config [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--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. |
--patches string |
| Path 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
25 -
Run post upgrade tasks
Synopsis
Run post upgrade tasks
kubeadm upgrade node phase post-upgrade [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
--dry-run |
| Do not change any state, just output the actions that would be performed. |
-h, --help |
| help 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
26 -
Run upgrade node pre-flight checks
Synopsis
Run pre-flight checks for kubeadm upgrade node.
kubeadm upgrade node phase preflight [flags]
Options
--config string |
| Path to a kubeadm configuration file. |
-h, --help |
| help for preflight |
--ignore-preflight-errors strings |
| A 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 string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |
27 -
Check which versions are available to upgrade to and validate whether your current cluster is upgradeable.
Synopsis
Check which versions are available to upgrade to and validate whether your current cluster is upgradeable. This command can only run on the control plane nodes where the kubeconfig file "admin.conf" exists. To skip the internet check, pass in the optional [version] parameter.
kubeadm upgrade plan [version] [flags]
Options
--allow-experimental-upgrades |
| Show unstable versions of Kubernetes as an upgrade alternative and allow upgrading to an alpha/beta/release candidate versions of Kubernetes. |
--allow-missing-template-keys Default: true |
| If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. |
--allow-release-candidate-upgrades |
| Show release candidate versions of Kubernetes as an upgrade alternative and allow upgrading to a release candidate versions of Kubernetes. |
--config string |
| Path to a kubeadm configuration file. |
-h, --help |
| help for plan |
--ignore-preflight-errors strings |
| A 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. |
-o, --output string Default: "text" |
| Output format. One of: text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file. |
--print-config |
| Specifies whether the configuration file that will be used in the upgrade should be printed or not. |
--show-managed-fields |
| If true, keep the managedFields when printing objects in JSON or YAML format. |
Options inherited from parent commands
--rootfs string |
| The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. |