Kubernetes news

 1,) Kubernetes drops Docker support

- Docker support in kubelet is now depreceted and will be removed in a future release. The kubelet uses a module called "dockershim" which implements CRI support for Docker and it has seen maintnance issues in the Kubernetes community. We encourage you to evaluate moving to a container runtime that is a full-fledged implementation of CRI(v1alpha1 or v1 compliant) as they become avaible.


a) What does that mean?

-Docker is just one of those container runtimes, but it is most popular, made containers popular

-build of docker:

Docker Engine

-CLI

-API

-Server

    *Container Runtime

    *Volumes

    *Network

    *build images

- Kubernetes need only one component from Docker -> Container Runtime

- dockershim 

    *how kubernetes is communicating with Docker

    *implements  CRI support for Docker  

    *part supportet by kubernetes

    *this part will be deprecated      


Container Rubtimes alternatives?

- containerd

    *containerd code was part of Docker Deamon

    *Docker extracted containerd as a separate component

    * it is part of CNCF

    *2nd most popular container runtime

    * is already used in Managed K8s services

-crio

    *used by openshift


What does this change mean for Kubernetes Users ? (DevOps Engineering, Developer)

-if your job is to instaling resources on an existing K8s cluster it doesn't affect you or no action is requierd


What does this change mean for Kubernetes Administrators ? (DevOps Engineer, Sys Admin)

- if your job is to setup Kubernetes cluster or to configure Kubernetes  cluster  and you have self-managed cluster - action is requiered! And if container runtime was docker you have two options:

    *substitiute Docker

    *install dockershim

- if you are using Cloud managed Kubernetes Cluster no action needed



When do you need to take action?

-Docker support depreceted since Kubernetes version 1.20

-for now you just get a warning 


Can I still use Docker in Kubernetes 1.20?

Yes, the only thing changing in 1.20 is a single warning log printed at kubelet startup if using Docker as the runtime.


When will dockershim be removed?

Given the impact of this change, we are using an extended deprecation timeline. It will not be removed before Kubernetes 1.22, meaning the earliest relese without dockershim would be 1.23 in late 2021. We will bw working closely with vendors and other ecosystem groups to  ensure a smooth transition and will evaluate things as the situation evolves.


What does this change mean for Minikube and Docker Desktop?

-it doesn't affect you and no action required 

What does theis change mean for CI/CD Pipelines?

-every Docker Image can run on any Container Runtime



How is this possible? 

-OCI (Open Container Initiative)

-standards around container technology

-Docker , containerd, CRI-O comply to these OCI standards 


b) Why did k8s drop support?

c) impact for you?


Komentarze

Popularne posty z tego bloga

Kubernetes

Helm

Ansible Tower / AWX