From 7c94a6f689ef6615f9270068a41d94e39096584d Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Fri, 28 Sep 2018 13:34:26 -0500 Subject: [PATCH 1/3] Remove network policies blurb from namespaces chatper There is now a dedicated chapter about network policies, so the two very rough slides on that topic should be removed from the namespaces chapter. --- slides/k8s/namespaces.md | 28 ---------------------------- 1 file changed, 28 deletions(-) diff --git a/slides/k8s/namespaces.md b/slides/k8s/namespaces.md index e08d007c..6c82b7bb 100644 --- a/slides/k8s/namespaces.md +++ b/slides/k8s/namespaces.md @@ -175,34 +175,6 @@ Note: it might take a minute or two for the app to be up and running. --- -## Network policies overview - -- We can create as many network policies as we want - -- Each network policy has: - - - a *pod selector*: "which pods are targeted by the policy?" - - - lists of ingress and/or egress rules: "which peers and ports are allowed or blocked?" - -- If a pod is not targeted by any policy, traffic is allowed by default - -- If a pod is targeted by at least one policy, traffic must be allowed explicitly - ---- - -## More about network policies - -- This remains a high level overview of network policies - -- For more details, check: - - - the [Kubernetes documentation about network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) - - - this [talk about network policies at KubeCon 2017 US](https://www.youtube.com/watch?v=3gGpMmYeEO8) by [@ahmetb](https://twitter.com/ahmetb) - ---- - ## Switch back to the default namespace - Let's make sure that we don't run future exercises in the `blue` namespace From 29a3ce0ba29b3c5d64c594c224c4d2e8b615d7c5 Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Mon, 10 Sep 2018 03:29:21 -0500 Subject: [PATCH 2/3] Update last chapter (what's next) --- slides/k8s/whatsnext.md | 53 +++++++++++++++++++++++++++++++++++------ 1 file changed, 46 insertions(+), 7 deletions(-) diff --git a/slides/k8s/whatsnext.md b/slides/k8s/whatsnext.md index b2eba31e..5f9cfe03 100644 --- a/slides/k8s/whatsnext.md +++ b/slides/k8s/whatsnext.md @@ -20,6 +20,43 @@ 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...) + + (price: $, difficulty: medium) + +- Hire someone to deploy it for us + + (price: $$, difficulty: easy) + +- Do it ourselves + + (price: $-$$$, dificulty: hard) + +--- + +## One big cluster vs. multiple small ones + +- Yes, it is possible to have prod+dev in a single cluster + + (and implement good isolation and security with RBAC, network policies...) + +- But it is not a good idea to do that for our first deployment + +- Start with a production cluster + at least a test cluster + +- Implement and check RBAC and isolation on the test cluster + + (e.g. deploy multiple test versions side-by-side) + +- 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 @@ -62,15 +99,19 @@ And *then* it is time to look at orchestration! ## Stateful services (second take) -- If you really want to host stateful services on Kubernetes, you can look into: +- If we want to host stateful services on Kubernetes, we can use: - - volumes (to carry persistent data) + - a storage provider - - storage plugins + - persistent volumes, persistent volume claims - - persistent volume claims (to ask for specific volume characteristics) + - stateful sets - - stateful sets (pods that are *not* ephemeral) +- Good questions to ask: + + - what's the *operational cost* of running this service ourselves? + + - what do we gain by deploying this stateful service on Kubernetes? --- @@ -123,8 +164,6 @@ And *then* it is time to look at orchestration! (but is being [deprecated](https://github.com/kubernetes/heapster/blob/master/docs/deprecation.md) starting with Kubernetes 1.11) - - --- ## Managing the configuration of our applications From f68194227c4aa773a54ee10730d3fe34fcb513eb Mon Sep 17 00:00:00 2001 From: Bridget Kromhout Date: Fri, 28 Sep 2018 08:13:59 -0500 Subject: [PATCH 3/3] Update whatsnext.md Typo fix, and clarity since it's not always being delivered by only one person. --- slides/k8s/whatsnext.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/slides/k8s/whatsnext.md b/slides/k8s/whatsnext.md index 5f9cfe03..384220a2 100644 --- a/slides/k8s/whatsnext.md +++ b/slides/k8s/whatsnext.md @@ -33,7 +33,7 @@ And *then* it is time to look at orchestration! - Do it ourselves - (price: $-$$$, dificulty: hard) + (price: $-$$$, difficulty: hard) --- @@ -240,7 +240,7 @@ Sorry Star Trek fans, this is not the federation you're looking for! ## Developer experience -*I've put this last, but it's pretty important!* +*We've put this last, but it's pretty important!* - How do you on-board a new developer?