Kubernetes Container Runtime Concepts: Difference between revisions
| Line 10: | Line 10: | ||
=Container Runtime= | =Container Runtime= | ||
Each Kubernetes [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Container_Runtime|node]] runs a container runtime, usually Docker. However, support for other container runtimes is available, via | Each Kubernetes [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Container_Runtime|node]] runs a container runtime, usually Docker. However, support for other container runtimes is available, via [[#CRI|Container Runtime Interface (CRI)]]. A container runtime performs container-related tasks such as pulling images and starting and stopping containers. | ||
A container runtime performs container-related tasks such as pulling images and starting and stopping containers. | |||
=<span id='CRI'></span>Container Runtime Interface (CRI)= | =<span id='CRI'></span>Container Runtime Interface (CRI)= | ||
Revision as of 21:26, 21 August 2019
External
Internal
Container Runtime
Each Kubernetes node runs a container runtime, usually Docker. However, support for other container runtimes is available, via Container Runtime Interface (CRI). A container runtime performs container-related tasks such as pulling images and starting and stopping containers.
Container Runtime Interface (CRI)
Runtime Classes
Runtime classes is a feature that was introduced in Kubernetes 1.2. It allows for different classes of runtimes (gVisor, Kata Containers, etc).
Docker
Kubernetes and Docker are complementary technologies. Docker is the technology that starts and stops containers under Kubernetes' supervision. Kubernetes is the higher-level technology that decides which nodes to run containers on, when to scale an application up or down or when to apply updates.
containerd
A container runtime that consists in a stripped-down version of Docker.