套件：cri-o（1.30.6+ds1-0elxr2）

Open Container Initiative-based implementation of Kubernetes Container Runtime Interface

CRI-O - OCI-based implementation of Kubernetes Container Runtime Interface

What is the scope of this project?

CRI-O is meant to provide an integration path between OCI conformant runtimes and the Kubelet. Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes. The scope of CRI-O is tied to the scope of the CRI.

At a high level, we expect the scope of CRI-O to be restricted to the following functionalities:

 * Support multiple image formats including the existing Docker image format
 * Support for multiple means to download images including trust &
   image verification
 * Container image management (managing image layers, overlay
   filesystems, etc)
 * Container process lifecycle management
 * Monitoring and logging required to satisfy the CRI
 * Resource isolation as required by the CRI

What is not in scope for this project?

 * Building, signing and pushing images to various image storages
 * A CLI utility for interacting with CRI-O. Any CLIs built as part of this
   project are only meant for testing this project and there will be no
   guarantees on the backward compatibility with it.

CRI-O is an implementation of the Kubernetes Container Runtime Interface (CRI) that will allow Kubernetes to directly launch and manage Open Container Initiative (OCI) containers.

The plan is to use OCI projects and best of breed libraries for different aspects:

 * Runtime: runc (or any OCI runtime  *spec implementation) and oci runtime
   tools
 * Images: Image management using containers/image
 * Storage: Storage and management of image layers using containers/storage
 * Networking: Networking support through the use of CNI

It is currently in active development in the Kubernetes community through the design proposal. Questions and issues should be raised in the Kubernetes sig-node Slack channel.

本頁面還能應用以下各種語言瀏覽: