Authors: Jorge Castro, Duffie Cooley, Kat Cosgrove, Justin Garrison, Noah Kantrowitz, Bob Killen, Rey Lejano, Dan “POP” Papandrea, Jeffrey Sica, Davanum “Dims” Srinivas
Kubernetes is deprecating Docker as a container runtime after v1.20.
You do not need to panic. It’s not as dramatic as it sounds.
TL;DR Docker as an underlying runtime is being deprecated in favor of runtimes that use the Container Runtime Interface (CRI) created for Kubernetes. Docker-produced images will continue to work in your cluster with all runtimes, as they always have.

Kubernetes is an open-source container orchestration platform for automating the deployment, scaling, and management of containerized applications. With Kubernetes, developers can deploy applications across clusters of machines, ensuring high availability, scalability, and resilience. Developers can learn about Kubernetes' architecture, core concepts, and deployment strategies, and gain hands-on experience with managing containerized workloads using Kubernetes.

Kubernetes

Kubernetes is deprecating Docker as a container runtime after v1.20. Docker is still a useful tool for building containers, and the images that result from running docker build can still run in your Kubernetes cluster. If you’re rolling your own clusters, you will need to make changes to avoid your clusters breaking.

Blog: Don't Panic: Kubernetes and Docker

<p>Still unclear why anyone should be calm, if it can’t be clearly stated that a simple Dockerfile will always keep working.</p>
