diff --git a/slides/k8s/daemonset.md b/slides/k8s/daemonset.md index 0a49875d..a12d3613 100644 --- a/slides/k8s/daemonset.md +++ b/slides/k8s/daemonset.md @@ -344,7 +344,7 @@ to the associated load balancer. - Show detailed information about the `rng` replica:
(The second command doesn't require you to get the exact name of the replica set) ```bash - kubectl describe rs rng-yyyy + kubectl describe rs rng-yyyyyyyy kubectl describe rs -l run=rng ``` diff --git a/slides/k8s/kubectlexpose.md b/slides/k8s/kubectlexpose.md index 21e728fe..3c1737de 100644 --- a/slides/k8s/kubectlexpose.md +++ b/slides/k8s/kubectlexpose.md @@ -151,7 +151,7 @@ The `-w` option "watches" events happening on the specified resources. -- -Our requests are load balanced across multiple pods. +Try it a few times! Our requests are load balanced across multiple pods. --- diff --git a/slides/k8s/logs-cli.md b/slides/k8s/logs-cli.md index 732d83f4..3d540304 100644 --- a/slides/k8s/logs-cli.md +++ b/slides/k8s/logs-cli.md @@ -59,7 +59,7 @@ Exactly what we need! - If it is not installed, the easiest method is to download a [binary release](https://github.com/wercker/stern/releases) -- The following commands will install Stern on a Linux Intel 64 bits machine: +- The following commands will install Stern on a Linux Intel 64 bit machine: ```bash sudo curl -L -o /usr/local/bin/stern \ https://github.com/wercker/stern/releases/download/1.8.0/stern_linux_amd64 diff --git a/slides/k8s/ourapponkube.md b/slides/k8s/ourapponkube.md index 531a7857..d562dec2 100644 --- a/slides/k8s/ourapponkube.md +++ b/slides/k8s/ourapponkube.md @@ -327,4 +327,8 @@ We should now see the `worker`, well, working happily. -- +Yes, this may take a little while to update. *(Narrator: it was DNS.)* + +-- + *Alright, we're back to where we started, when we were running on a single node!* diff --git a/slides/k8s/rollout.md b/slides/k8s/rollout.md index 5765338e..b01111b4 100644 --- a/slides/k8s/rollout.md +++ b/slides/k8s/rollout.md @@ -71,7 +71,7 @@ cd ~/container.training/stacks ``` -- Edit `dockercoins/worker/worker.py`, update the `sleep` line to sleep 1 second +- Edit `dockercoins/worker/worker.py`; update the first `sleep` line to sleep 1 second - Build a new tag and push it to the registry: ```bash diff --git a/slides/k8s/whatsnext.md b/slides/k8s/whatsnext.md index 384220a2..d6d597b8 100644 --- a/slides/k8s/whatsnext.md +++ b/slides/k8s/whatsnext.md @@ -1,26 +1,3 @@ -# Next steps - -*Alright, how do I get started and containerize my apps?* - --- - -Suggested containerization checklist: - -.checklist[ -- write a Dockerfile for one service in one app -- write Dockerfiles for the other (buildable) services -- write a Compose file for that whole app -- make sure that devs are empowered to run the app in containers -- set up automated builds of container images from the code repo -- set up a CI pipeline using these container images -- set up a CD pipeline (for staging/QA) using these images -] - -And *then* it is time to look at orchestration! - ---- - - ## Options for our first production cluster - Get a managed cluster from a major cloud provider (AKS, EKS, GKE...) @@ -53,27 +30,7 @@ And *then* it is time to look at orchestration! - Make sure that all our devs have usable dev clusters - (wether it's a local minikube or a full-blown multi-node cluster) - ---- - -## Namespaces - -- Namespaces let you run multiple identical stacks side by side - -- Two namespaces (e.g. `blue` and `green`) can each have their own `redis` service - -- Each of the two `redis` services has its own `ClusterIP` - -- CoreDNS creates two entries, mapping to these two `ClusterIP` addresses: - - `redis.blue.svc.cluster.local` and `redis.green.svc.cluster.local` - -- Pods in the `blue` namespace get a *search suffix* of `blue.svc.cluster.local` - -- As a result, resolving `redis` from a pod in the `blue` namespace yields the "local" `redis` - -.warning[This does not provide *isolation*! That would be the job of network policies.] + (whether it's a local minikube or a full-blown multi-node cluster) --- @@ -236,16 +193,3 @@ Sorry Star Trek fans, this is not the federation you're looking for! - Discover resources across clusters ---- - -## Developer experience - -*We've put this last, but it's pretty important!* - -- How do you on-board a new developer? - -- What do they need to install to get a dev stack? - -- How does a code change make it from dev to prod? - -- How does someone add a component to a stack?