text: The architecture overview that is shown in Figure 2-13 includes the following components: 
  
  (cid:2) Pods are managed by a Kubelet that is based on information that is received from 
  
  Kubernetes. The Kubelet and CRI-O communicate over CRI-gRPC API. Each pod hosts 
  one or more containers from same cgroup and share common resources that are available 
  in Pod.CRI-O uses CIN plug-in for network setup for the pod. 
  
  (cid:2) CRI-O daemon starts a new pod that is based on Kubelet instructions that are received by 
  way of Kubernetes CRI, which pulls images from the Container registry. 
  
  (cid:2) The Container library unpacks the downloaded image in the Container root file system and 
  stores it in the COW file system. 
  
  (cid:2) After rootfs is created for container by using OCI generate tools, CRI-O creates JSON 
  
  files with a runtime specification for the pod. The OCI-compatible run time is started based 
  on the runtime specification. The default OCI run time is runc. 
  
  (cid:2) Containers are monitored by using a common process that handles logging for the 
  container process until the exit code ends the process. 
  
  (cid:2) GitHub repository for several CRI-O components provides the following components: 