Mostly reformatting so that slides are nice and tidy

slides/kube/daemonset.md

@@ -4,16 +4,30 @@
 
 - We want one (and exactly one) instance of `rng` per node
 
-- If we just scale `deploy/rng` to the number of worker nodes in our cluster, nothing guarantees that the rng processes will be distributed evenly across the cluster
+- What if we just scale up `deploy/rng` to the number of nodes?
+
+  - nothing guarantees that the `rng` containers will be distributed evenly
+
+  - if we add nodes later, they will not automatically run a copy of `rng`
+
+  - if we remove (or reboot) a node, one `rng` container will restart elsewhere
 
 - Instead of a `deployment`, we will use a `daemonset`
 
+---
+
+## Daemon sets in practice
+
 - Daemon sets are great for cluster-wide, per-node processes:
 
   - `kube-proxy`
+
   - `weave` (our overlay network)
+
   - monitoring agents
+
   - hardware management tools (e.g. SCSI/FC HBA agents)
+
   - etc.
 
 - They can also be restricted to run [only on some nodes](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#running-pods-on-only-some-nodes)

slides/kube/dashboard.md

@@ -89,18 +89,30 @@ The goo.gl URL expands to:
 
 - Connect to https://oneofournodes:3xxxx/
 
-  - Yes, https. If you use http it will say:
-
-              This page isn’t working
-              <oneofournodes> sent an invalid response.
-              ERR_INVALID_HTTP_RESPONSE
-
-  - You will have to work around the TLS certificate validation warning
+- You will have to work around the TLS certificate validation warning
 
 <!-- ```open https://node1:3xxxx/``` -->
 
 ]
 
+The dashboard will then ask you which authentication you want to use.
+
+.warning[Make sure that you use `https`! Otherwise, you'll get this error:]
+
+```
+This page isn’t working
+<oneofournodes> sent an invalid response.
+ERR_INVALID_HTTP_RESPONSE
+```
+
+.warning[Chrome 63 (and later) as well as recent versions of Edge will refuse to connect.]
+
+We do not know how to work around that issue for the moment.
+
+---
+
+## Dashboard authentication
+
 - We have three authentication options at this point:
 
   - token (associated with a role that has appropriate permissions)

slides/kube/kubectlget.md

@@ -136,7 +136,8 @@ There is already one service on our cluster: the Kubernetes API itself.
   ```
   
   - `-k` is used to skip certificate verification
-  - Make sure to replace 10.96.0.1 with the CLUSTER-IP shown by `$ kubectl get svc`
+
+  - Make sure to replace 10.96.0.1 with the CLUSTER-IP shown by `kubectl get svc`
 
 ]
 

slides/kube/setup-k8s.md

@@ -50,6 +50,8 @@
 
 - If you are on AWS:
   [EKS](https://aws.amazon.com/eks/)
+  or
+  [kops](https://github.com/kubernetes/kops)
 
 - On a local machine:
   [minikube](https://kubernetes.io/docs/getting-started-guides/minikube/),