Minor tweaks for kadm content

slides/k8s/architecture.md

@@ -165,6 +165,25 @@ What does that mean?
 
 ---
 
+## Let's experiment a bit!
+
+- For the exercises in this section, connect to the first node of the `test` cluster
+
+.exercise[
+
+- SSH to the first node of the test cluster
+
+- Check that the cluster is operational:
+  ```bash
+  kubectl get nodes
+  ```
+
+- All nodes should be `Ready`
+
+]
+
+---
+
 ## Create
 
 - Let's create a simple object

slides/k8s/cluster-upgrade.md

@@ -18,6 +18,8 @@
 
 .exercise[
 
+- Log into node `test1`
+
 - Check the version of kubectl and of the API server:
   ```bash
   kubectl version

slides/k8s/cni.md

@@ -650,7 +650,8 @@ For critical services, we might want to precisely control the update process.
 
 - We can see informative messages in the output of kube-router:
   ```
-  time="2019-04-07T15:53:56Z" level=info msg="Peer Up" Key=X.X.X.X State=BGP_FSM_OPENCONFIRM Topic=Peer
+  time="2019-04-07T15:53:56Z" level=info msg="Peer Up"
+  Key=X.X.X.X State=BGP_FSM_OPENCONFIRM Topic=Peer
   ```
 
 - We should see the routes of the other clusters show up

slides/k8s/dmuc.md

@@ -33,7 +33,7 @@
 
 ## Our environment
 
-- We will use the machine indicated as `dmuc`
+- We will use the machine indicated as `dmuc1`
 
   (this stands for "Dessine Moi Un Cluster" or "Draw Me A Sheep",
   <br/>in homage to Saint-Exupery's "The Little Prince")
@@ -54,7 +54,7 @@
 
 .exercise[
 
-- Log into the `dmuc` machine
+- Log into the `dmuc1` machine
 
 - Get root:
   ```bash
@@ -106,7 +106,7 @@
 - Try to start the API server:
   ```bash
   kube-apiserver
-  # It will fail with --etcd-servers must be specified
+  # It will fail with "--etcd-servers must be specified"
   ```
 
 ]
@@ -559,7 +559,7 @@ Success!
 
 Our node should show up.
 
-Its name will be its hostname (it should be `dmuc`).
+Its name will be its hostname (it should be `dmuc1`).
 
 ---