官术网_书友最值得收藏!

  • Learn OpenShift
  • Denis Zuev Artemii Kropachev Aleksey Usov
  • 220字
  • 2021-08-13 16:03:55

How CRI-O works with Kubernetes

When you want to start or stop a container with Kubernetes, Kubernetes talks to CRI-O, and CRI-O talks to an OCI-compliant container runtime such as runc for Docker to start a container. CRI-O can also pull OCI-compliant container images and manage them on a disk. Good news for Container Developers—they do not need to work with CRI-O directly, as Kubernetes handles that automatically. But it is important to understand the concept and overall architecture:

CRI-O architecture

To sum this up, there are a few things to note before we go to the hands-on part and install CRI-O in our lab:

  • Kubernetes is configured to talk to CRI-O to launch a new Pod in a container environment
  • CRI-O pulls the OCI-compliant Container Image, if necessary, from a registry and manages it locally
  • CRI-O talks to OCI-compliant Container Runtime (runc, by default) to run it on a Kubernetes Node
  • Container Runtime starts the container from a container image that's talking to a Linux Kernel
  • Linux Kernel starts Container Processes such as an inappropriate namespace, group, context, and so on
  • Each container is monitored and logged by a separate process controlled by Linux Kernel
  • The networking part for containers is controlled by a Container Network Interface (CNI) that can be used by CRI-O as well
主站蜘蛛池模板: 兴隆县| 衢州市| 安新县| 伊春市| 三都| 南汇区| 荆门市| 石屏县| 高要市| 四子王旗| 崇文区| 宣武区| 松滋市| 普兰店市| 沁水县| 阿尔山市| 双牌县| 菏泽市| 郎溪县| 凤冈县| 锦州市| 无极县| 淄博市| 济阳县| 微山县| 拜城县| 武义县| 山阳县| 深泽县| 军事| 建平县| 阆中市| 抚州市| 丰台区| 新乡市| 栾城县| 柘荣县| 宿迁市| 同仁县| 连江县| 安乡县|