KCNA · Question #177
Which of the following container runtime is planned to be deprecated in Kubernetes 1.20 and high- er?
The correct answer is C. docker. Kubernetes versions 1.20 and higher began deprecating Docker as a container runtime because the kubelet interacts with runtimes via the Container Runtime Interface (CRI), which Docker does not directly implement.
Question
Which of the following container runtime is planned to be deprecated in Kubernetes 1.20 and high- er?
Options
- Acri-o
- BNone of the options
- Cdocker
- Dpodman
- Econtainerd
How the community answered
(35 responses)- A6% (2)
- C89% (31)
- D3% (1)
- E3% (1)
Why each option
Kubernetes versions 1.20 and higher began deprecating Docker as a container runtime because the kubelet interacts with runtimes via the Container Runtime Interface (CRI), which Docker does not directly implement.
cri-o is a CRI-compliant container runtime that integrates directly with Kubernetes and is not being deprecated.
This option is incorrect as Docker was indeed deprecated.
Kubernetes 1.20 and higher deprecated Docker as a container runtime because the kubelet uses the Container Runtime Interface (CRI) to interact with container runtimes. Docker does not natively implement CRI; instead, an adapter (dockershim) was used, which was removed from kubelet starting with Kubernetes 1.24.
Podman is a daemonless container engine not directly used by Kubernetes as its primary runtime in the same way Docker was, and it is not being deprecated by Kubernetes.
containerd is a core component of Docker and is a CRI-compliant container runtime widely used in Kubernetes clusters, and is not being deprecated.
Concept tested: Kubernetes container runtime deprecation
Source: https://kubernetes.io/blog/2020/12/02/dockershim-deprecation-faq/
Topics
Community Discussion
No community discussion yet for this question.