1KUBERNETES(1)(kubernetes) KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7
9 kubeadm upgrade apply - Upgrade your Kubernetes cluster to the speci‐
10 fied version
11
12
13
15 kubeadm upgrade apply [OPTIONS]
16
17
18
20 Upgrade your Kubernetes cluster to the specified version
21
22
23
25 --allow-experimental-upgrades=false Show unstable versions of Ku‐
26 bernetes as an upgrade alternative and allow upgrading to an al‐
27 pha/beta/release candidate versions of Kubernetes.
28
29
30 --allow-release-candidate-upgrades=false Show release candidate
31 versions of Kubernetes as an upgrade alternative and allow upgrading to
32 a release candidate versions of Kubernetes.
33
34
35 --certificate-renewal=true Perform the renewal of certificates
36 used by component changed during upgrades.
37
38
39 --config="" Path to a kubeadm configuration file.
40
41
42 --dry-run=false Do not change any state, just output what actions
43 would be performed.
44
45
46 --etcd-upgrade=true Perform the upgrade of etcd.
47
48
49 --feature-gates="" A set of key=value pairs that describe feature
50 gates for various features. Options are: PublicKeysECDSA=true|false
51 (ALPHA - default=false) RootlessControlPlane=true|false (ALPHA - de‐
52 fault=false) UnversionedKubeletConfigMap=true|false (default=true)
53
54
55 -f, --force=false Force upgrading although some requirements might
56 not be met. This also implies non-interactive mode.
57
58
59 --ignore-preflight-errors=[] A list of checks whose errors will be
60 shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ig‐
61 nores errors from all checks.
62
63
64 --kubeconfig="/etc/kubernetes/admin.conf" The kubeconfig file to
65 use when talking to the cluster. If the flag is not set, a set of stan‐
66 dard locations can be searched for an existing kubeconfig file.
67
68
69 --patches="" Path to a directory that contains files named "tar‐
70 get[suffix][+patchtype].extension". For example, "kube-apis‐
71 erver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-
72 apiserver", "kube-controller-manager", "kube-scheduler", "etcd",
73 "kubeletconfiguration". "patchtype" can be one of "strategic", "merge"
74 or "json" and they match the patch formats supported by kubectl. The
75 default "patchtype" is "strategic". "extension" must be either "json"
76 or "yaml". "suffix" is an optional string that can be used to determine
77 which patches are applied first alpha-numerically.
78
79
80 --print-config=false Specifies whether the configuration file that
81 will be used in the upgrade should be printed or not.
82
83
84 -y, --yes=false Perform the upgrade and do not prompt for confir‐
85 mation (non-interactive mode).
86
87
88
90 --azure-container-registry-config="" Path to the file containing
91 Azure container registry configuration information.
92
93
94 --rootfs="" [EXPERIMENTAL] The path to the 'real' host root
95 filesystem.
96
97
98 --version=false Print version information and quit
99
100
101
103 kubeadm-upgrade(1),
104
105
106
108 January 2015, Originally compiled by Eric Paris (eparis at redhat dot
109 com) based on the kubernetes source material, but hopefully they have
110 been automatically generated since!
111
112
113
114Manuals User KUBERNETES(1)(kubernetes)