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 --experimental-patches="" Path to a directory that contains files
43 named "target[suffix][+patchtype].extension". For example, "kube-apis‐
44 erver0+merge.yaml" or just "etcd.json". "patchtype" can be one of
45 "strategic", "merge" or "json" and they match the patch formats sup‐
46 ported by kubectl. The default "patchtype" is "strategic". "extension"
47 must be either "json" or "yaml". "suffix" is an optional string that
48 can be used to determine which patches are applied first alpha-numeri‐
49 cally.
50
51
52
54 --azure-container-registry-config="" Path to the file containing
55 Azure container registry configuration information.
56
57
58 --log-flush-frequency=5s Maximum number of seconds between log
59 flushes
60
61
62 --rootfs="" [EXPERIMENTAL] The path to the 'real' host root
63 filesystem.
64
65
66 --version=false Print version information and quit
67
68
69
71 kubeadm-join-phase-control-plane-prepare(1),
72
73
74
76 January 2015, Originally compiled by Eric Paris (eparis at redhat dot
77 com) based on the kubernetes source material, but hopefully they have
78 been automatically generated since!
79
80
81
82Manuals User KUBERNETES(1)(kubernetes)