@@ -34,7 +34,7 @@ store your cluster's configuration and authorities.
34
34
35
35
Now, create an ISO:
36
36
37
- $ spire iso gen preseeded.iso building/ ~/.ssh/id_rsa.pub
37
+ $ spire iso gen preseeded.iso ~/.ssh/id_rsa.pub # this key is used for direct access during cluster setup
38
38
39
39
Now you should burn and/or upload preseeded.iso that you've just gotten, so
40
40
that you can use it for installing servers. Make a note of the password it
@@ -73,10 +73,7 @@ For the official homeworld servers:
73
73
* Configure the supervisor keyserver:
74
74
75
75
$ spire setup keyserver
76
-
77
- * Check that the keyserver is running properly:
78
-
79
- $ spire verify keystatics
76
+ $ spire verify keystatics # make sure the keyserver is running
80
77
81
78
* Admit the supervisor node to the cluster:
82
79
@@ -93,7 +90,6 @@ For the official homeworld servers:
93
90
94
91
$ spire access update-known-hosts # set up certificate authority in ~/.ssh/known_hosts
95
92
$ spire access ssh # if this fails, you might need to make sure you don't have any stale kerberos tickets
96
- $ ssh-keygen -L -f ~/.ssh/id_rsa-cert.pub
97
93
98
94
* Configure and test SSH:
99
95
@@ -142,10 +138,11 @@ For the official homeworld servers:
142
138
member 439721bf885a52a5 is healthy: got healthy result from https://18.181.0.104:2379
143
139
member 61712dffdce48432 is healthy: got healthy result from https://18.181.0.97:2379
144
140
member f6d798ec325cf15d is healthy: got healthy result from https://18.181.0.106:2379
141
+ cluster is healthy
145
142
146
143
* Query etcd cluster members:
147
144
148
- $ spire etcdctl cluster-health member list
145
+ $ spire etcdctl member list
149
146
439721bf885a52a5: name=huevos-rancheros peerURLs=https://18.181.0.104:2380 clientURLs=https://18.181.0.104:2379 isLeader=false
150
147
61712dffdce48432: name=eggs-benedict peerURLs=https://18.181.0.97:2380 clientURLs=https://18.181.0.97:2379 isLeader=true
151
148
f6d798ec325cf15d: name=ole-miss peerURLs=https://18.181.0.106:2380 clientURLs=https://18.181.0.106:2379 isLeader=false
@@ -189,7 +186,8 @@ DNS, but when that happens, you can turn it back off:
189
186
190
187
## Bootstrap cluster registry
191
188
192
- $ ln -s .../keys-for-homeworld.mit.edu/ $HOMEWORLD_DIR/https-certs
189
+ $ mkdir $HOMEWORLD_DIR/https-certs
190
+ $ cp homeworld.mit.edu.key homeworld.mit.edu.pem $HOMEWORLD_DIR/https-certs
193
191
$ spire setup bootstrap-registry
194
192
195
193
## Confirm container launching
@@ -203,12 +201,13 @@ DNS, but when that happens, you can turn it back off:
203
201
204
202
Deploy flannel into the cluster:
205
203
206
- $ cd deployment/deployment-config/cluster-gen/
207
- $ hyperkube kubectl create -f flannel.yaml
204
+ $ mkdir cluster-gen
205
+ $ spire config gen-kube cluster-gen
206
+ $ spire kubectl create -f cluster-gen/flannel.yaml
208
207
209
208
Wait a bit for propagation.
210
209
211
- $ hyperkube kubectl get pods --namespace=kube-system
210
+ $ spire kubectl get pods --namespace=kube-system
212
211
NAME READY STATUS RESTARTS AGE
213
212
kube-flannel-ds-1r1cx 1/1 Running 0 49s
214
213
kube-flannel-ds-2cxj5 1/1 Running 0 49s
@@ -219,7 +218,7 @@ Wait a bit for propagation.
219
218
220
219
Verify flannel functionality by running flannel tests on two different nodes:
221
220
222
- $ # two nodes
221
+ $ # on two different nodes
223
222
$ ssh root@<worker>.mit.edu
224
223
# rkt run --debug --interactive=true --net=rkt.kubernetes.io homeworld.mit.edu/debian
225
224
$ ip addr # make sure this provides a 172.18 IP, and not a 172.16 IP.
@@ -231,11 +230,11 @@ If the ping works both ways, then flannel works! At least at a basic level.
231
230
232
231
Deploy dns-addon into the cluster:
233
232
234
- $ hyperkube kubectl create -f dns-addon.yaml
233
+ $ spire kubectl create -f dns-addon.yaml
235
234
236
235
Wait for deployment to succeed:
237
236
238
- $ hyperkube kubectl get pods --namespace=kube-system
237
+ $ spire kubectl get pods --namespace=kube-system
239
238
NAME READY STATUS RESTARTS AGE
240
239
kube-dns-v20-69lrg 3/3 Running 0 1m
241
240
kube-dns-v20-clh2z 3/3 Running 0 1m
0 commit comments