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

NAME

9       kubeadm  upgrade  node  phase control-plane - Upgrade the control plane
10       instance deployed on this node, if any
11
12
13

SYNOPSIS

15       kubeadm upgrade node phase control-plane [OPTIONS]
16
17
18

DESCRIPTION

20       Upgrade the control plane instance deployed on this node, if any
21
22
23

OPTIONS

25       --certificate-renewal=true      Perform  the  renewal  of  certificates
26       used by component changed during upgrades.
27
28
29       --dry-run=false       Do  not change any state, just output the actions
30       that would be performed.
31
32
33       --etcd-upgrade=true      Perform the upgrade of etcd.
34
35
36       --kubeconfig="/etc/kubernetes/admin.conf"      The kubeconfig  file  to
37       use when talking to the cluster. If the flag is not set, a set of stan‐
38       dard locations can be searched for an existing kubeconfig file.
39
40
41       --patches=""      Path to a directory that contains files  named  "tar‐
42       get[suffix][+patchtype].extension".     For     example,    "kube-apis‐
43       erver0+merge.yaml" or just "etcd.json". "target" can be one  of  "kube-
44       apiserver",    "kube-controller-manager",   "kube-scheduler",   "etcd".
45       "patchtype" can be one of "strategic", "merge" or "json" and they match
46       the  patch  formats  supported  by  kubectl. The default "patchtype" is
47       "strategic". "extension" must be either "json" or "yaml".  "suffix"  is
48       an  optional string that can be used to determine which patches are ap‐
49       plied first alpha-numerically.
50
51
52

OPTIONS INHERITED FROM PARENT COMMANDS

54       --azure-container-registry-config=""      Path to the  file  containing
55       Azure container registry configuration information.
56
57
58       --rootfs=""       [EXPERIMENTAL]  The  path  to  the  'real'  host root
59       filesystem.
60
61
62       --version=false      Print version information and quit
63
64
65

SEE ALSO

67       kubeadm-upgrade-node-phase(1),
68
69
70

HISTORY

72       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
73       com)  based  on the kubernetes source material, but hopefully they have
74       been automatically generated since!
75
76
77
78Manuals                              User            KUBERNETES(1)(kubernetes)