Skip to content

Commit 7a3b970

Browse files
Merge pull request kubernetes#852 from gg7/scratch-improvements
"Custom Cluster from Scratch" improvements
2 parents 9a1f3d4 + c6ad7e5 commit 7a3b970

File tree

1 file changed

+20
-15
lines changed

1 file changed

+20
-15
lines changed

Diff for: docs/getting-started-guides/scratch.md

+20-15
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,7 @@ be active at once. Note that you can grow the end of this range, but you
111111
cannot move it without disrupting the services and pods that already use it.
112112

113113
Also, you need to pick a static IP for master node.
114+
114115
- Call this `MASTER_IP`.
115116
- Open any firewalls to allow access to the apiserver ports 80 and/or 443.
116117
- Enable ipv4 forwarding sysctl, `net.ipv4.ip_forward = 1`
@@ -184,11 +185,11 @@ For etcd, you can:
184185

185186
We recommend that you use the etcd version which is provided in the Kubernetes binary distribution. The Kubernetes binaries in the release
186187
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`.
188189

189190
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):
190191

191-
- `HYPERKUBE_IMAGE==gcr.io/google_containers/hyperkube:$TAG`
192+
- `HYPERKUBE_IMAGE=gcr.io/google_containers/hyperkube:$TAG`
192193
- `ETCD_IMAGE=gcr.io/google_containers/etcd:$ETCD_VERSION`
193194

194195
### Security Models
@@ -213,11 +214,10 @@ You need to prepare several certs:
213214
- The kubelets optionally need certs to identify themselves as clients of the master, and when
214215
serving its own API over HTTPS.
215216

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
220-
`cluster/saltbase/salt/generate-cert/make-cert.sh`
217+
Unless you plan to have a real CA generate your certs, you will need
218+
to generate a root cert and use that to sign the master, kubelet, and
219+
kubectl certs. How to do this is described in the [authentication
220+
documentation](/docs/admin/authentication/#creating-certificates).
221221

222222
You will end up with the following files (we will use these variables later on)
223223

@@ -285,7 +285,7 @@ users:
285285
clusters:
286286
- name: local
287287
cluster:
288-
certificate-authority-data: ${CA_CERT_BASE64_ENCODED}
288+
certificate-authority: /srv/kubernetes/ca.crt
289289
contexts:
290290
- context:
291291
cluster: local
@@ -558,8 +558,10 @@ For each of these components, the steps to start them running are similar:
558558
],
559559
"livenessProbe": {
560560
"httpGet": {
561-
"path": "/healthz",
562-
"port": 8080
561+
"scheme": "HTTP",
562+
"host": "127.0.0.1",
563+
"port": 8080,
564+
"path": "/healthz"
563565
},
564566
"initialDelaySeconds": 15,
565567
"timeoutSeconds": 15
@@ -605,6 +607,7 @@ If you are following the firewall-only security approach, then use these argumen
605607
- `--advertise-address=$MASTER_IP`
606608

607609
If you are using the HTTPS approach, then set:
610+
608611
- `--client-ca-file=/srv/kubernetes/ca.crt`
609612
- `--token-auth-file=/srv/kubernetes/known_tokens.csv`
610613
- `--basic-auth-file=/srv/kubernetes/basic_auth.csv`
@@ -666,9 +669,10 @@ Complete this template for the scheduler pod:
666669
],
667670
"livenessProbe": {
668671
"httpGet": {
669-
"host" : "127.0.0.1",
670-
"path": "/healthz",
671-
"port": 10251
672+
"scheme": "HTTP",
673+
"host": "127.0.0.1",
674+
"port": 10251,
675+
"path": "/healthz"
672676
},
673677
"initialDelaySeconds": 15,
674678
"timeoutSeconds": 15
@@ -721,9 +725,10 @@ Template for controller manager pod:
721725
],
722726
"livenessProbe": {
723727
"httpGet": {
728+
"scheme": "HTTP",
724729
"host": "127.0.0.1",
725-
"path": "/healthz",
726-
"port": 10252
730+
"port": 10252,
731+
"path": "/healthz"
727732
},
728733
"initialDelaySeconds": 15,
729734
"timeoutSeconds": 15

0 commit comments

Comments
 (0)