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. If
32       not set the default network interface will be used.
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       --certificate-key=""
49           Key used to encrypt the control-plane certificates in the
50       kubeadm-certs Secret.
51
52
53       --control-plane-endpoint=""
54           Specify a stable IP address or DNS name for the control plane.
55
56
57       --cri-socket=""
58           Path to the CRI socket to connect. If empty kubeadm will try to
59       auto-detect this value; use this option only if you have more than one
60       CRI installed or if you have non-standard CRI socket.
61
62
63       --feature-gates=""
64           A set of key=value pairs that describe feature gates for various
65       features. Options are: IPv6DualStack=true|false (ALPHA - default=false)
66       PublicKeysECDSA=true|false (ALPHA - default=false)
67
68
69       --kubernetes-version="stable-1"
70           Choose a specific Kubernetes version for the control plane.
71
72
73       --node-name=""
74           Specify the node name.
75
76
77       --pod-network-cidr=""
78           Specify range of IP addresses for the pod network. If set, the
79       control plane will automatically allocate CIDRs for every node.
80
81
82       --service-cidr="10.96.0.0/12"
83           Use alternative range of IP address for service VIPs.
84
85
86       --service-dns-domain="cluster.local"
87           Use alternative domain for services, e.g. "myorg.internal".
88
89
90

OPTIONS INHERITED FROM PARENT COMMANDS

92       --azure-container-registry-config=""
93           Path to the file containing Azure container registry configuration
94       information.
95
96
97       --kubeconfig="/etc/kubernetes/admin.conf"
98           The kubeconfig file to use when talking to the cluster. If the flag
99       is not set, a set of standard locations can be searched for an existing
100       kubeconfig file.
101
102
103       --log-flush-frequency=5s
104           Maximum number of seconds between log flushes
105
106
107       --rootfs=""
108           [EXPERIMENTAL] The path to the 'real' host root filesystem.
109
110
111       --version=false
112           Print version information and quit
113
114
115

HISTORY

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

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

OPTIONS INHERITED FROM PARENT COMMANDS

SEE ALSO

HISTORY