-
Notifications
You must be signed in to change notification settings - Fork 14.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add documentation for CRI API moving to v1beta1
Signed-off-by: Mrunal Patel <[email protected]>
- Loading branch information
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
25 changes: 25 additions & 0 deletions
25
content/en/docs/concepts/containers/container-runtime-interface.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
|
||
--- | ||
reviewers: | ||
- dchen1107 | ||
- derekwaynecarr | ||
title: Container Runtime Interface | ||
content_type: concept | ||
weight: 20 | ||
--- | ||
|
||
<!-- overview --> | ||
|
||
{{< feature-state for_k8s_version="v1.20" state="beta" >}} | ||
|
||
This page describes the Container Runtime Interface (CRI). | ||
|
||
kubelet communicates with a container runtime such as docker, containerd or CRI-O over the CRI | ||
API. CRI is a grpc API with kubelet as the client and a container runtime implmenting the | ||
server side. | ||
|
||
CRI consists of an image service and a runtime service. | ||
|
||
The runtime service is for managing pods and containers. | ||
|
||
The image service is concerned with managing images for containers. |