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:  PublicKeysECDSA=true|false
58       (ALPHA  -  default=false)  RootlessControlPlane=true|false (ALPHA - de‐
59       fault=false)   UnversionedKubeletConfigMap=true|false   (BETA   -   de‐
60       fault=true)
61
62
63       --image-repository="k8s.gcr.io"       Choose  a  container  registry to
64       pull control plane images from
65
66
67       --kubernetes-version="stable-1"      Choose a specific Kubernetes  ver‐
68       sion for the control plane.
69
70
71       --patches=""       Path  to a directory that contains files named "tar‐
72       get[suffix][+patchtype].extension".    For     example,     "kube-apis‐
73       erver0+merge.yaml"  or  just "etcd.json". "target" can be one of "kube-
74       apiserver",   "kube-controller-manager",   "kube-scheduler",    "etcd".
75       "patchtype" can be one of "strategic", "merge" or "json" and they match
76       the patch formats supported by  kubectl.  The  default  "patchtype"  is
77       "strategic".  "extension"  must be either "json" or "yaml". "suffix" is
78       an optional string that can be used to determine which patches are  ap‐
79       plied first alpha-numerically.
80
81
82       --pod-network-cidr=""       Specify  range  of IP addresses for the pod
83       network. If set, the control plane will  automatically  allocate  CIDRs
84       for every node.
85
86
87       --scheduler-extra-args=      A set of extra flags to pass to the Sched‐
88       uler or override default ones in form of =
89
90
91       --service-cidr="10.96.0.0/12"      Use alternative range of IP  address
92       for service VIPs.
93
94
95

OPTIONS INHERITED FROM PARENT COMMANDS

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

EXAMPLE

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

SEE ALSO

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

HISTORY

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