Kubernetes 1.20 is deprecating Docker Runtime: What does this mean?

Between November 11th and December 4th, there was widespread confusion regarding Kubernetes dropping Docker support, but the reality is less alarming. Kubernetes is not dropping Docker entirely but is deprecating the Docker runtime, specifically Dockershim, which was always meant to be a temporary implementation to facilitate Docker's integration. This change has been planned for years, aiming to transition towards more efficient container runtimes like Containerd and CRI-O, which are part of the Open Container Initiative. Developers and users of services like Azure Kubernetes Service or Elastic Kubernetes Service will experience minimal disruption, as Docker functionalities such as Dockerfiles, Docker Compose, and Dockerhub will continue to operate as usual. Kubernetes 1.20 will officially deprecate Dockershim, with a warning message appearing for users still on the Docker runtime, and the earliest version without Dockershim is expected in late 2021 with Kubernetes 1.23. While developers will hardly notice the shift, Kubernetes cluster administrators will need to transition to a CRI-compliant runtime, but this adjustment is considered a positive move towards eliminating inefficiencies and simplifying Kubernetes maintenance.