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       -k, --experimental-kustomize=""
42           The path where kustomize patches for static pod manifests are
43       stored.
44
45
46

OPTIONS INHERITED FROM PARENT COMMANDS

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

SEE ALSO

67       kubeadm-join-phase-control-plane-prepare(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
78Eric Paris                  kubernetes User Manuals              KUBERNETES(1)