Merge pull request #374 from bridgetkromhout/velny-k8s101-2018

Velny k8s101 2018 updates

slides/k8s/links-bridget.md

@@ -1,15 +1,13 @@
 # Links and resources
 
-- [Kubernetes Community](https://kubernetes.io/community/) - Slack, Google Groups, meetups
-
-- [Kubernetes on StackOverflow](https://stackoverflow.com/questions/tagged/kubernetes)
-
-- [Play With Kubernetes Hands-On Labs](https://medium.com/@marcosnils/introducing-pwk-play-with-k8s-159fcfeb787b)
+- [Microsoft Learn](https://docs.microsoft.com/learn/)
 
 - [Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/)
 
 - [Cloud Developer Advocates](https://developer.microsoft.com/advocates/)
 
+- [Kubernetes Community](https://kubernetes.io/community/) - Slack, Google Groups, meetups
+
 - [Local meetups](https://www.meetup.com/)
 
 - [devopsdays](https://www.devopsdays.org/)

slides/k8s/namespaces.md

@@ -227,3 +227,21 @@ Note: it might take a minute or two for the app to be up and running.
 - On our clusters, they are installed as `kns` and `kctx`
 
   (for brevity and to avoid completion clashes between `kubectx` and `kubectl`)
+
+---
+
+## `kube-ps1`
+
+- It's easy to lose track of our current cluster / context / namespace
+
+- `kube-ps1` makes it easy to track these, by showing them in our shell prompt
+
+- It's a simple shell script available from https://github.com/jonmosco/kube-ps1
+
+- On our clusters, `kube-ps1` is installed and included in `PS1`:
+  ```
+  [123.45.67.89] `(kubernetes-admin@kubernetes:default)` docker@node1 ~
+  ```
+  (The highlighted part is `context:namespace`, managed by `kube-ps1`)
+
+- Highly recommended if you work across multiple contexts or namespaces!