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

  • 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
主站蜘蛛池模板: 枞阳县| 久治县| 石泉县| 宝山区| 宾阳县| 益阳市| 云南省| 襄汾县| 林周县| 台南市| 钟山县| 连南| 洪湖市| 松滋市| 静乐县| 朝阳区| 德清县| 泗洪县| 高尔夫| 乐业县| 宁阳县| 阳原县| 泉州市| 曲松县| 临沭县| 永寿县| 专栏| 文成县| 信阳市| 宣汉县| 渭源县| 南部县| 讷河市| 卓尼县| 潞西市| 马鞍山市| 浦北县| 拉萨市| 西宁市| 汉川市| 海安县|