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

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

NAME

9       kubeadm  init  phase control-plane apiserver - Generates the kube-apis‐
10       erver static Pod manifest
11
12
13

SYNOPSIS

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

DESCRIPTION

20       Generates the kube-apiserver static Pod manifest
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       --dry-run=false      Don't apply any changes; just output what would be
49       done.
50
51
52       --feature-gates=""      A set of key=value pairs that describe  feature
53       gates  for  various  features.  Options are: EtcdLearnerMode=true|false
54       (ALPHA  -  default=false)  PublicKeysECDSA=true|false  (ALPHA   -   de‐
55       fault=false) RootlessControlPlane=true|false (ALPHA - default=false)
56
57
58       --image-repository="registry.k8s.io"       Choose  a container registry
59       to pull control plane images from
60
61
62       --kubernetes-version="stable-1"      Choose a specific Kubernetes  ver‐
63       sion for the control plane.
64
65
66       --patches=""       Path  to a directory that contains files named "tar‐
67       get[suffix][+patchtype].extension".    For     example,     "kube-apis‐
68       erver0+merge.yaml"  or  just "etcd.json". "target" can be one of "kube-
69       apiserver",   "kube-controller-manager",   "kube-scheduler",    "etcd",
70       "kubeletconfiguration".  "patchtype" can be one of "strategic", "merge"
71       or "json" and they match the patch formats supported  by  kubectl.  The
72       default  "patchtype"  is "strategic". "extension" must be either "json"
73       or "yaml". "suffix" is an optional string that can be used to determine
74       which patches are applied first alpha-numerically.
75
76
77       --service-cidr="10.96.0.0/12"       Use alternative range of IP address
78       for service VIPs.
79
80
81

OPTIONS INHERITED FROM PARENT COMMANDS

83       --azure-container-registry-config=""      Path to the  file  containing
84       Azure container registry configuration information.
85
86
87       --rootfs=""       [EXPERIMENTAL]  The  path  to  the  'real'  host root
88       filesystem.
89
90
91       --version=false      Print version information and quit
92
93
94

HISTORY

101       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
102       com)  based  on the kubernetes source material, but hopefully they have
103       been automatically generated since!
104
105
106
107Manuals                              User            KUBERNETES(1)(kubernetes)

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

OPTIONS INHERITED FROM PARENT COMMANDS

SEE ALSO

HISTORY