Fix Ingress section

slides/wek8s/ingress.md

@@ -202,19 +202,21 @@ We should see an Ingress resource appear in the output.
 
 ---
 
-## Access the service
+## Something's wrong ...
 
-- Go back to the browser tab where we were loading webui.A.B.C.D.nip.io
+- In the Traefik web UI, at this point, we may see an error
 
-- Hit reload ...
+  (the backend is highlighted in red)
 
-- ... And we should we the web UI for DockerCoins!
+- What's happening?
+
+- Let's try and find out!
 
 ---
 
-## What does an Ingress look like?
+## Inspecting the Ingress
 
-- Let's inspect the Ingress generated by the generic service chart!
+- Let's look at the Ingress generated by the generic service chart
 
 .exercise[
 
@@ -225,6 +227,38 @@ We should see an Ingress resource appear in the output.
 
 ]
 
+- Can you see the problem?
+
+--
+
+- It still refers to `webui-service` instead of `webui`!
+
+---
+
+## Fixing the Ingress
+
+- We need to edit the chart (again)
+
+.exercise[
+
+- Find the file defining the Ingress resource
+
+- Make the necessary changes
+
+- Upgrade the `webui` release with the new chart
+
+]
+
+---
+
+## Access the service
+
+- Go back to the browser tab where we were loading webui.A.B.C.D.nip.io
+
+- Hit reload ...
+
+- ... And we should we the web UI for DockerCoins!
+
 ---
 
 ## Creating an Ingress by hand

slides/wek8s/switchback.md

@@ -0,0 +1,3 @@
+## Get back to node1
+
+- From now on, it is recommended to log back into `node1`

slides/wwrk.yml

@@ -104,6 +104,7 @@ chapters:
   - k8s/accessinternal.md
   - wek8s/helm.md
   - wek8s/ingress.md
+  - wek8s/switchback.md
 - - k8s/prometheus.md
   - k8s/volumes.md
   - k8s/configuration.md