Read on Twitter
Me and the rest of the internet today.
I always say that container runtimes are the most important thing I feel like people should talk about more than we do, and here we are! Be sure to check out @_inductor_'s awesome blog, "Wait, Docker is deprecated in Kubernetes now? What do I do?" https://dev.to/inductor/wait-docker-is-deprecated-in-kubernetes-now-what-do-i-do-e4m
Here's my sparknotes on the situation, and there will be a blog out soon with more detail, which I will link to. Unfortunately, "container runtime" is a bit overloaded and its context helps shape what it means. But it's always VERY important!
1)Kubernetes is capable of running many different kinds of containers! The container runtime you choose has a big impact on the security style/expectations, the speed of spinning up containers, & on resource utilization. It's a critical piece of any container-based architecture.
2) Kubernetes does this by having an administrator configure the kubelet (worker node piece) with the container runtime type you’ll be using. Telling Kubernetes “just use Docker” will no longer be an option. But this is where it gets a little tricky.
“Docker” is an amazing usability tool. It provides a super convenient wrapper around the experience of working with containers. But Docker itself uses a container runtime to actually run containers - and that’s containerd!
Containerd itself plays nicely with Kubernetes. But when you tell Kubernetes “just use Docker”, it has to go through the usability wrapper part which makes the whole thing janky. So basically, Docker as a "container runtime" does not play nicely with Kubernetes.
So the ask here is: tell Kubernetes to run the container images you give it using a friendlier runtime, like containerd itself, or CRI-O. You can still build/develop with Docker, but Kubernetes will run those containers more directly, through a friendlier container runtime.
Be sure to check out @Dixie3Flatline's twitter thread on the topic - it's super awesome and has a smidge more detail! https://twitter.com/Dixie3Flatline/status/1334188913724850177
And the blog post is out! Learn more here! https://twitter.com/K8sContributors/status/1334301732830990336?s=19
