From 971314a84f6ae8ee0fcd20314bc74b35c25de5c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Wed, 13 Sep 2023 16:09:26 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A7=20Minor=20fixes=20in=20DMUC=20refa?= =?UTF-8?q?ctor?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- slides/k8s/dmuc-easy.md | 33 ++++++++++++++++++++++++++++++++- slides/k8s/dmuc-medium.md | 2 +- 2 files changed, 33 insertions(+), 2 deletions(-) diff --git a/slides/k8s/dmuc-easy.md b/slides/k8s/dmuc-easy.md index 001ad51d..07a7e90d 100644 --- a/slides/k8s/dmuc-easy.md +++ b/slides/k8s/dmuc-easy.md @@ -545,7 +545,38 @@ clusters: ] -Success! +If it works: great! + +If it complains about a "cgroup driver", check the next slide. + +--- + +## Cgroup drivers + +- Cgroups ("control groups") are a Linux kernel feature + +- They're used to account and limit resources + + (e.g.: memory, CPU, block I/O...) + +- There are multiple ways to manipulate cgroups, including: + + - through a pseudo-filesystem (typically mounted in /sys/fs/cgroup) + + - through systemd + +- Kubelet and the container engine need to agree on which method to use + +--- + +## Setting the cgroup driver + +- If kubelet refused to start, mentioning a cgroup driver issue, try: + ```bash + kubelet --kubeconfig ~/.kube/config --cgroup-driver=systemd + ``` + +- That *should* do the trick! --- diff --git a/slides/k8s/dmuc-medium.md b/slides/k8s/dmuc-medium.md index 70541513..2ae46664 100644 --- a/slides/k8s/dmuc-medium.md +++ b/slides/k8s/dmuc-medium.md @@ -873,7 +873,7 @@ This time, it should work. - Enable RBAC, and generate individual certificates for each controller - (check the [certificate paths][certpath] section in the Kubernetes documentatio + (check the [certificate paths][certpath] section in the Kubernetes documentation for a detailed list of all the certificates and keys that are used by the control plane, and which flags are used by which components to configure them!)