✂️ Remove ctr.run

slides/k8s/exercise-helm.md

@@ -10,7 +10,7 @@ Level 2: make it so that the number of replicas can be set with `--set replicas=
 
 Level 3: change the colors of the lego bricks.
 
-(For level 3, fork the repository and use ctr.run to build images.)
+(For level 3, you'll have to build/push your own images.)
 
 See next slide if you need hints!
 
@@ -44,20 +44,12 @@ Also add `replicas: 5` to `values.yaml` to provide a default value.
 
 ## Changing the color
 
-- Fork the repository
+- Create an account on e.g. Docker Hub (e.g. `janedoe`)
 
-- Make sure that your fork has valid Dockerfiles
-
-  (or identify a branch that has valid Dockerfiles)
-
-- Use the following images:
-
-  ctr.run/yourgithubusername/wordsmith/db:branchname
-
-  (replace db with web and words for the other components)
+- Create an image repository (e.g. `janedoe/web`)
 
 - Change the images and/or CSS in `web/static`
 
-- Commit, push, trigger a rolling update
+- Build and push
 
-  (`imagePullPolicy` should be `Always`, which is the default)
+- Trigger a rolling update using the image you just pushed

slides/k8s/shippingimages.md

@@ -94,28 +94,20 @@
 
 ## Building on the fly
 
-- Some services can build images on the fly from a repository
+- Conceptually, it is possible to build images on the fly from a repository
 
 - Example: [ctr.run](https://ctr.run/)
 
-.exercise[
+  (deprecated in August 2020, after being aquired by Datadog)
 
-- Use ctr.run to automatically build a container image and run it:
+- It did allow something like this:
   ```bash
   docker run ctr.run/github.com/jpetazzo/container.training/dockercoins/hasher
   ```
 
-<!--
-```longwait Sinatra```
-```key ^C```
--->
+- No alternative yet
 
-]
-
-There might be a long pause before the first layer is pulled,
-because the API behind `docker pull` doesn't allow to stream build logs, and there is no feedback during the build.
-
-It is possible to view the build logs by setting up an account on [ctr.run](https://ctr.run/).
+  (free startup idea, anyone?)
 
 ???