kubeadm-config-upload-from-flags(1)

1KUBERNETES(1)                      Jan 2015                      KUBERNETES(1)
2
3
4

NAME

6       kubeadm  config upload from-flags - Create the in-cluster configuration
7       file for the first time from using flags.
8
9
10

SYNOPSIS

12       kubeadm config upload from-flags [OPTIONS]
13
14
15

DESCRIPTION

17       Using this command, you can upload configuration to  the  ConfigMap  in
18       the  cluster  using  the same flags you gave to 'kubeadm init'.  If you
19       initialized your cluster using a v1.7.x or lower kubeadm client and set
20       certain  flags, you need to run this command with the same flags before
21       upgrading to v1.8 using 'kubeadm upgrade'.
22
23
24       The configuration is located in  the  "kube-system"  namespace  in  the
25       "kubeadm-config" ConfigMap.
26
27
28

OPTIONS

30       --apiserver-advertise-address=""
31           The  IP  address  the  API Server will advertise it's listening on.
32       Specify '0.0.0.0' to use the address of the default network interface.
33
34
35       --apiserver-bind-port=6443
36           Port for the API Server to bind to.
37
38
39       --apiserver-cert-extra-sans=[]
40           Optional extra Subject Alternative Names (SANs) to use for the  API
41       Server serving certificate. Can be both IP addresses and DNS names.
42
43
44       --cert-dir="/etc/kubernetes/pki"
45           The path where to save and store the certificates.
46
47
48       --cri-socket="/var/run/dockershim.sock"
49           Specify the CRI socket to connect to.
50
51
52       --feature-gates=""
53           A  set  of  key=value pairs that describe feature gates for various
54       features. Options  are:  Auditing=true|false  (ALPHA  -  default=false)
55       CoreDNS=true|false (default=true) DynamicKubeletConfig=true|false (BETA
56       - default=false)
57
58
59       --kubernetes-version="stable-1"
60           Choose a specific Kubernetes version for the control plane.
61
62
63       --node-name=""
64           Specify the node name.
65
66
67       --pod-network-cidr=""
68           Specify range of IP addresses for the pod network. If set, the con‐
69       trol plane will automatically allocate CIDRs for every node.
70
71
72       --service-cidr="10.96.0.0/12"
73           Use alternative range of IP address for service VIPs.
74
75
76       --service-dns-domain="cluster.local"
77           Use alternative domain for services, e.g. "myorg.internal".
78
79
80

OPTIONS INHERITED FROM PARENT COMMANDS

82       --azure-container-registry-config=""
83           Path  to the file containing Azure container registry configuration
84       information.
85
86
87       --google-json-key=""
88           The Google Cloud Platform Service  Account  JSON  Key  to  use  for
89       authentication.
90
91
92       --kubeconfig="/etc/kubernetes/admin.conf"
93           The KubeConfig file to use when talking to the cluster. If the flag
94       is not set, a set of standard locations are searched  for  an  existing
95       KubeConfig file.
96
97
98       --log-flush-frequency=5s
99           Maximum number of seconds between log flushes
100
101
102       --rootfs=""
103           [EXPERIMENTAL] The path to the 'real' host root filesystem.
104
105
106       --version=false
107           Print version information and quit
108
109
110

HISTORY

117       January  2015,  Originally compiled by Eric Paris (eparis at redhat dot
118       com) based on the kubernetes source material, but hopefully  they  have
119       been automatically generated since!
120
121
122
123Eric Paris                  kubernetes User Manuals              KUBERNETES(1)

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

OPTIONS INHERITED FROM PARENT COMMANDS

SEE ALSO

HISTORY