1KUBERNETES(1)                      Jan 2015                      KUBERNETES(1)
2
3
4

NAME

6       kubeadm  join  phase control-plane-prepare control-plane - Generate the
7       manifests for the new control plane components
8
9
10

SYNOPSIS

12       kubeadm join phase control-plane-prepare control-plane [OPTIONS]
13
14
15

DESCRIPTION

17       Generate the manifests for the new control plane components
18
19
20

OPTIONS

22       --apiserver-advertise-address=""
23           If the node should host  a  new  control  plane  instance,  the  IP
24       address the API Server will advertise it's listening on. If not set the
25       default network interface will be used.
26
27
28       --apiserver-bind-port=6443
29           If the node should host a new control plane instance, the port  for
30       the API Server to bind to.
31
32
33       --config=""
34           Path to kubeadm config file.
35
36
37       --control-plane=false
38           Create a new control plane instance on this node
39
40
41       --experimental-control-plane=false
42           Create a new control plane instance on this node
43
44
45

OPTIONS INHERITED FROM PARENT COMMANDS

47       --azure-container-registry-config=""
48           Path  to the file containing Azure container registry configuration
49       information.
50
51
52       --log-flush-frequency=5s
53           Maximum number of seconds between log flushes
54
55
56       --rootfs=""
57           [EXPERIMENTAL] The path to the 'real' host root filesystem.
58
59
60       --version=false
61           Print version information and quit
62
63
64

SEE ALSO

66       kubeadm-join-phase-control-plane-prepare(1),
67
68
69

HISTORY

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