- 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
推薦閱讀
- 操作系統實用教程(Linux版)
- Mastering ElasticSearch
- Kali Linux滲透測試全流程詳解
- 嵌入式Linux系統開發:基于Yocto Project
- Alfresco 4 Enterprise Content Management Implementation
- Windows 7中文版從入門到精通(修訂版)
- 操作系統分析
- Hands-On GPU Programming with Python and CUDA
- Linux操作系統
- Linux 從入門到項目實踐(超值版)
- Linux網絡操作系統項目教程(RHEL 7.4/CentOS 7.4)(第3版)(微課版)
- Implementing Cloud Design Patterns for AWS(Second Edition)
- Mastering AWS CloudFormation
- Apache ShardingSphere權威指南
- 不可不知的Windows技巧