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:
55
56
57       --kubernetes-version="stable-1"
58           Choose a specific Kubernetes version for the control plane.
59
60
61       --node-name=""
62           Specify the node name.
63
64
65       --pod-network-cidr=""
66           Specify range of IP addresses for the pod network. If set, the con‐
67       trol plane will automatically allocate CIDRs for every node.
68
69
70       --service-cidr="10.96.0.0/12"
71           Use alternative range of IP address for service VIPs.
72
73
74       --service-dns-domain="cluster.local"
75           Use alternative domain for services, e.g. "myorg.internal".
76
77
78

OPTIONS INHERITED FROM PARENT COMMANDS

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

SEE ALSO

105       kubeadm-config-upload(1),
106
107
108

HISTORY

110       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
111       com)  based  on the kubernetes source material, but hopefully they have
112       been automatically generated since!
113
114
115
116Eric Paris                  kubernetes User Manuals              KUBERNETES(1)