You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recommend that you use the etcd version which is provided in the Kubernetes binary distribution. The Kubernetes binaries in the release
186
187
were tested extensively with this version of etcd and not with any other version.
187
-
The recommended version number can also be found as the value of `ETCD_VERSION` in `kubernetes/cluster/images/etcd/Makefile`.
188
+
The recommended version number can also be found as the value of `TAG` in `kubernetes/cluster/images/etcd/Makefile`.
188
189
189
190
The remainder of the document assumes that the image identifiers have been chosen and stored in corresponding env vars. Examples (replace with latest tags and appropriate registry):
@@ -213,11 +214,10 @@ You need to prepare several certs:
213
214
- The kubelets optionally need certs to identify themselves as clients of the master, and when
214
215
serving its own API over HTTPS.
215
216
216
-
Unless you plan to have a real CA generate your certs, you will need to generate a root cert and use that to sign the master, kubelet, and kubectl certs.
217
-
218
-
- see function `create-certs` in `cluster/common.sh`
219
-
- see also `cluster/saltbase/salt/generate-cert/make-ca-cert.sh` and
0 commit comments