From 40cd934118302d4cbec77e8bcf26ffcec8aea0bc Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Wed, 5 Dec 2018 14:25:19 -0600 Subject: [PATCH] Add a slide explaining tradeoffs between static/normal pods for control plane --- slides/k8s/staticpods.md | 23 ++++++++++++++++++++++- slides/kube-twodays.yml | 1 + 2 files changed, 23 insertions(+), 1 deletion(-) diff --git a/slides/k8s/staticpods.md b/slides/k8s/staticpods.md index a65f2f34..f1e179e3 100644 --- a/slides/k8s/staticpods.md +++ b/slides/k8s/staticpods.md @@ -155,6 +155,28 @@ --- +## Where should the control plane be? + +*Is it better to run the control plane in static pods, or normal pods?* + +- If I'm a *user* of the cluster: I don't care, it makes no difference to me + +- What if I'm an *admin*, i.e. the person who installs, upgraes, repairs... the cluster? + +- If I'm using a managed Kubernetes cluster (AKS, EKS, GKE...) it's not my problem + + (I'm not the one setting up and managing the control plane) + +- If I already picked a tool (kubeadm, kops...) to setup my cluster, the tool decides for me + +- What if I haven't picked a tool yet, or if I'm installing from scratch? + + - static pods = easier to set up, easier to troubleshoot, less risk of outage + + - normal pods = easier to upgrade, easier to move (if nodes need to be shutdown) + +--- + ## Static pods in action - On our clusters, the `staticPodPath` is `/etc/kubernetes/manifests` @@ -215,4 +237,3 @@ The `-node1` suffix was added automatically by kubelet. If we delete the pod (with `kubectl delete`), it will be recreated immediately. To delete the pod, we need to delete (or move) the manifest file. - diff --git a/slides/kube-twodays.yml b/slides/kube-twodays.yml index 0da90e1b..01eb1fa4 100644 --- a/slides/kube-twodays.yml +++ b/slides/kube-twodays.yml @@ -57,6 +57,7 @@ chapters: - - k8s/owners-and-dependents.md - k8s/statefulsets.md - k8s/portworx.md + - k8s/staticpods.md - - k8s/whatsnext.md - k8s/links.md - shared/thankyou.md