1KUBERNETES(1)(kubernetes) KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7
9 kubeadm join phase control-plane-prepare control-plane - Generate the
10 manifests for the new control plane components
11
12
13
15 kubeadm join phase control-plane-prepare control-plane [OPTIONS]
16
17
18
20 Generate the manifests for the new control plane components
21
22
23
25 --apiserver-advertise-address="" If the node should host a new
26 control plane instance, the IP address the API Server will advertise
27 it's listening on. If not set the default network interface will be
28 used.
29
30
31 --apiserver-bind-port=6443 If the node should host a new control
32 plane instance, the port for the API Server to bind to.
33
34
35 --config="" Path to kubeadm config file.
36
37
38 --control-plane=false Create a new control plane instance on this
39 node
40
41
42 --patches="" Path to a directory that contains files named "tar‐
43 get[suffix][+patchtype].extension". For example, "kube-apis‐
44 erver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-
45 apiserver", "kube-controller-manager", "kube-scheduler", "etcd".
46 "patchtype" can be one of "strategic", "merge" or "json" and they match
47 the patch formats supported by kubectl. The default "patchtype" is
48 "strategic". "extension" must be either "json" or "yaml". "suffix" is
49 an optional string that can be used to determine which patches are ap‐
50 plied first alpha-numerically.
51
52
53
55 --azure-container-registry-config="" Path to the file containing
56 Azure container registry configuration information.
57
58
59 --rootfs="" [EXPERIMENTAL] The path to the 'real' host root
60 filesystem.
61
62
63 --version=false Print version information and quit
64
65
66
68 kubeadm-join-phase-control-plane-prepare(1),
69
70
71
73 January 2015, Originally compiled by Eric Paris (eparis at redhat dot
74 com) based on the kubernetes source material, but hopefully they have
75 been automatically generated since!
76
77
78
79Manuals User KUBERNETES(1)(kubernetes)