1KUBERNETES(1)(kubernetes)                            KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7

NAME

9       kubeadm upgrade node - Upgrade commands for a node in the cluster
10
11
12

SYNOPSIS

14       kubeadm upgrade node [OPTIONS]
15
16
17

DESCRIPTION

19       Upgrade commands for a node in the cluster
20
21
22       The "node" command executes the following phases:
23
24
25              preflight       Run upgrade node pre-flight checks
26              control-plane   Upgrade the control plane instance deployed on this node, if any
27              kubelet-config  Upgrade the kubelet configuration for this node
28
29
30
31

OPTIONS

33       --certificate-renewal=true       Perform  the  renewal  of certificates
34       used by component changed during upgrades.
35
36
37       --dry-run=false      Do not change any state, just output  the  actions
38       that would be performed.
39
40
41       --etcd-upgrade=true      Perform the upgrade of etcd.
42
43
44       --ignore-preflight-errors=[]      A list of checks whose errors will be
45       shown as warnings. Example: 'IsPrivilegedUser,Swap'.  Value  'all'  ig‐
46       nores errors from all checks.
47
48
49       --kubeconfig="/etc/kubernetes/admin.conf"       The  kubeconfig file to
50       use when talking to the cluster. If the flag is not set, a set of stan‐
51       dard locations can be searched for an existing kubeconfig file.
52
53
54       --patches=""       Path  to a directory that contains files named "tar‐
55       get[suffix][+patchtype].extension".    For     example,     "kube-apis‐
56       erver0+merge.yaml"  or  just "etcd.json". "target" can be one of "kube-
57       apiserver",   "kube-controller-manager",   "kube-scheduler",    "etcd",
58       "kubeletconfiguration".  "patchtype" can be one of "strategic", "merge"
59       or "json" and they match the patch formats supported  by  kubectl.  The
60       default  "patchtype"  is "strategic". "extension" must be either "json"
61       or "yaml". "suffix" is an optional string that can be used to determine
62       which patches are applied first alpha-numerically.
63
64
65       --skip-phases=[]      List of phases to be skipped
66
67
68

OPTIONS INHERITED FROM PARENT COMMANDS

70       --azure-container-registry-config=""       Path  to the file containing
71       Azure container registry configuration information.
72
73
74       --rootfs=""      [EXPERIMENTAL]  The  path  to  the  'real'  host  root
75       filesystem.
76
77
78       --version=false      Print version information and quit
79
80
81

SEE ALSO

83       kubeadm-upgrade(1), kubeadm-upgrade-node-phase(1),
84
85
86

HISTORY

88       January  2015,  Originally compiled by Eric Paris (eparis at redhat dot
89       com) based on the kubernetes source material, but hopefully  they  have
90       been automatically generated since!
91
92
93
94Manuals                              User            KUBERNETES(1)(kubernetes)
Impressum