Skip to content
This repository was archived by the owner on Mar 9, 2022. It is now read-only.

Commit c88e18b

Browse files
Fix architecture doc
Network namespace is created before the pause container. Signed-off-by: Aldo Culquicondor <[email protected]>
1 parent ec3aa44 commit c88e18b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ The `cri` plugin uses containerd to manage the full container lifecycle and all
99

1010
Let's use an example to demonstrate how the `cri` plugin works for the case when Kubelet creates a single-container pod:
1111
* 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;
1213
* `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;
1414
* Kubelet subsequently calls the `cri` plugin, via the CRI image service API, to pull the application container image;
1515
* `cri` further uses containerd to pull the image if the image is not present on the node;
1616
* 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

Comments
 (0)