kubeadm-init-phase-control-plane-all(1)

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       --experimental-patches=""      Path to a directory that contains  files
53       named  "target[suffix][+patchtype].extension". For example, "kube-apis‐
54       erver0+merge.yaml" or just  "etcd.json".  "patchtype"  can  be  one  of
55       "strategic",  "merge"  or  "json" and they match the patch formats sup‐
56       ported by kubectl. The default "patchtype" is "strategic".  "extension"
57       must  be  either  "json" or "yaml". "suffix" is an optional string that
58       can be used to determine which patches are applied first  alpha-numeri‐
59       cally.
60
61
62       --feature-gates=""       A set of key=value pairs that describe feature
63       gates for various features. Options are: IPv6DualStack=true|false  (AL‐
64       PHA - default=false) PublicKeysECDSA=true|false (ALPHA - default=false)
65
66
67       --image-repository="k8s.gcr.io"       Choose  a  container  registry to
68       pull control plane images from
69
70
71       --kubernetes-version="stable-1"      Choose a specific Kubernetes  ver‐
72       sion for the control plane.
73
74
75       --pod-network-cidr=""       Specify  range  of IP addresses for the pod
76       network. If set, the control plane will  automatically  allocate  CIDRs
77       for every node.
78
79
80       --scheduler-extra-args=      A set of extra flags to pass to the Sched‐
81       uler or override default ones in form of =
82
83
84       --service-cidr="10.96.0.0/12"      Use alternative range of IP  address
85       for service VIPs.
86
87
88

OPTIONS INHERITED FROM PARENT COMMANDS

90       --azure-container-registry-config=""       Path  to the file containing
91       Azure container registry configuration information.
92
93
94       --log-flush-frequency=5s      Maximum number  of  seconds  between  log
95       flushes
96
97
98       --rootfs=""       [EXPERIMENTAL]  The  path  to  the  'real'  host root
99       filesystem.
100
101
102       --version=false      Print version information and quit
103
104
105

EXAMPLE

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

HISTORY

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