You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 9, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: docs/architecture.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ The `cri` plugin uses containerd to manage the full container lifecycle and all
9
9
10
10
Let's use an example to demonstrate how the `cri` plugin works for the case when Kubelet creates a single-container pod:
11
11
* Kubelet calls the `cri` plugin, via the CRI runtime service API, to create a pod;
12
+
*`cri` creates and configures the pod’s network namespace using CNI;
12
13
*`cri` uses containerd internal to create and start a special [pause container](https://www.ianlewis.org/en/almighty-pause-container) (the sandbox container) and put that container inside the pod’s cgroups and namespace (steps omitted for brevity);
13
-
*`cri` configures the pod’s network namespace using CNI;
14
14
* Kubelet subsequently calls the `cri` plugin, via the CRI image service API, to pull the application container image;
15
15
*`cri` further uses containerd to pull the image if the image is not present on the node;
16
16
* Kubelet then calls `cri`, via the CRI runtime service API, to create and start the application container inside the pod using the pulled container image;
0 commit comments