From f046a32567b48d6aa052a18d8df9c9d4d51dfaf3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Mon, 5 Dec 2022 15:28:59 -0800 Subject: [PATCH] =?UTF-8?q?=F0=9F=90=8B=20Update=20info=20about=20Docker+K?= =?UTF-8?q?8S?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- slides/k8s/concepts-k8s.md | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/slides/k8s/concepts-k8s.md b/slides/k8s/concepts-k8s.md index adfc0336..13fab51a 100644 --- a/slides/k8s/concepts-k8s.md +++ b/slides/k8s/concepts-k8s.md @@ -287,7 +287,9 @@ No! -- -- By default, Kubernetes uses the Docker Engine to run containers +- The Docker Engine used to be the default option to run containers with Kubernetes + +- Support for Docker (specifically: dockershim) was removed in Kubernetes 1.24 - We can leverage other pluggable runtimes through the *Container Runtime Interface* @@ -329,32 +331,26 @@ Yes! - We can do these things without Docker
- (and get diagnosed with NIH¹ syndrome) + (but with some languages/frameworks, it might be much harder) - Docker is still the most stable container engine today
(but other options are maturing very quickly) -.footnote[¹[Not Invented Here](https://en.wikipedia.org/wiki/Not_invented_here)] - --- class: extra-details ## Do we need to run Docker at all? +- On our Kubernetes clusters: + + *Not anymore* + - On our development environments, CI pipelines ... : *Yes, almost certainly* -- On our production servers: - - *Yes (today)* - - *Probably not (in the future)* - -.footnote[More information about CRI [on the Kubernetes blog](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes)] - --- ## Interacting with Kubernetes