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

NAME

9       kubeadm init phase control-plane all - Generate all static Pod manifest
10       files
11
12
13

SYNOPSIS

15       kubeadm init phase control-plane all [OPTIONS]
16
17
18

DESCRIPTION

20       Generate all static Pod manifest files
21
22
23

OPTIONS

25       --apiserver-advertise-address=""      The IP  address  the  API  Server
26       will advertise it's listening on. If not set the default network inter‐
27       face will be used.
28
29
30       --apiserver-bind-port=6443      Port for the API Server to bind to.
31
32
33       --apiserver-extra-args=      A set of extra flags to pass  to  the  API
34       Server or override default ones in form of =
35
36
37       --cert-dir="/etc/kubernetes/pki"       The path where to save and store
38       the certificates.
39
40
41       --config=""      Path to a kubeadm configuration file.
42
43
44       --control-plane-endpoint=""      Specify a stable  IP  address  or  DNS
45       name for the control plane.
46
47
48       --controller-manager-extra-args=       A  set of extra flags to pass to
49       the Controller Manager or override default ones in form of =
50
51
52       --dry-run=false      Don't apply any changes; just output what would be
53       done.
54
55
56       --feature-gates=""       A set of key=value pairs that describe feature
57       gates for various  features.  Options  are:  EtcdLearnerMode=true|false
58       (ALPHA   -   default=false)  PublicKeysECDSA=true|false  (ALPHA  -  de‐
59       fault=false) RootlessControlPlane=true|false (ALPHA - default=false)
60
61
62       --image-repository="registry.k8s.io"      Choose a  container  registry
63       to pull control plane images from
64
65
66       --kubernetes-version="stable-1"       Choose a specific Kubernetes ver‐
67       sion for the control plane.
68
69
70       --patches=""      Path to a directory that contains files  named  "tar‐
71       get[suffix][+patchtype].extension".     For     example,    "kube-apis‐
72       erver0+merge.yaml" or just "etcd.json". "target" can be one  of  "kube-
73       apiserver",    "kube-controller-manager",   "kube-scheduler",   "etcd",
74       "kubeletconfiguration". "patchtype" can be one of "strategic",  "merge"
75       or  "json"  and  they match the patch formats supported by kubectl. The
76       default "patchtype" is "strategic". "extension" must be  either  "json"
77       or "yaml". "suffix" is an optional string that can be used to determine
78       which patches are applied first alpha-numerically.
79
80
81       --pod-network-cidr=""      Specify range of IP addresses  for  the  pod
82       network.  If  set,  the control plane will automatically allocate CIDRs
83       for every node.
84
85
86       --scheduler-extra-args=      A set of extra flags to pass to the Sched‐
87       uler or override default ones in form of =
88
89
90       --service-cidr="10.96.0.0/12"       Use alternative range of IP address
91       for service VIPs.
92
93
94

OPTIONS INHERITED FROM PARENT COMMANDS

96       --azure-container-registry-config=""      Path to the  file  containing
97       Azure container registry configuration information.
98
99
100       --rootfs=""       [EXPERIMENTAL]  The  path  to  the  'real'  host root
101       filesystem.
102
103
104       --version=false      Print version information and quit
105
106
107

EXAMPLE

109                # Generates all static Pod manifest files for control plane components,
110                # functionally equivalent to what is generated by kubeadm init.
111                kubeadm init phase control-plane all
112
113                # Generates all static Pod manifest files using options read from a configuration file.
114                kubeadm init phase control-plane all --config config.yaml
115
116
117
118

SEE ALSO

120       kubeadm-init-phase-control-plane(1),
121
122
123

HISTORY

125       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
126       com)  based  on the kubernetes source material, but hopefully they have
127       been automatically generated since!
128
129
130
131Manuals                              User            KUBERNETES(1)(kubernetes)
Impressum