- 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
推薦閱讀
- Kubernetes修煉手冊
- 白話區塊鏈
- Mastering Distributed Tracing
- 無蘋果不生活 OS X Mountain Lion隨身寶典
- 操作系統基礎與實踐:基于openEuler平臺
- Java EE 8 Design Patterns and Best Practices
- 竹林蹊徑:深入淺出windows驅動開發
- AutoCAD 2014中文版從入門到精通
- Windows Server 2012網絡操作系統項目教程(第4版)
- iOS 8開發指南
- CentOS 6 Linux Server Cookbook
- Linux 從入門到項目實踐(超值版)
- Web Penetration Testing with Kali Linux(Third Edition)
- 嵌入式微系統
- 應急指揮信息系統設計