vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
No description
257 commits 7 branches 27 tags 53 MiB
Go 67.7%
Shell 19.5%
C 8.5%
Dockerfile 1.6%
Makefile 1.5%
Other 1.2%
Find a file
Mrunal Patel 5a5be4b308 Merge pull request #69 from rhatdan/master 
Add man page for ocid
2016-09-28 14:30:13 -07:00
.tool Makefile: suggests install.tools 2016-09-28 20:53:29 +02:00
cmd Add client impl for listing containers 2016-09-27 15:17:56 -07:00
conmon conmon: booleans already from stdbool.h 2016-09-24 00:38:07 +02:00
docs Add man page for ocid 2016-09-28 16:22:28 -04:00
hack Update vendors to inclue golang.org/x/sys 2016-09-27 11:34:45 -07:00
oci Make sure that the container stops when StopContainer API is called 2016-09-27 11:46:05 -07:00
server Ensure containers are stopped on RemovePod 2016-09-28 13:12:38 -07:00
test Add a test for pod remove 2016-09-28 13:15:57 -07:00
utils Convert status to exit code 2016-09-19 12:25:13 -07:00
vendor/src Update vendors to inclue golang.org/x/sys 2016-09-27 11:34:45 -07:00
.gitignore Fix the build for ocid to cri-o rename 2016-09-26 16:55:12 -07:00
.travis.yml Build with "tip" version of Golang 2016-09-28 13:11:41 -07:00
code-of-conduct.md Add a code of conduct based on github.com/kubernetes/kubernetes 2016-09-09 15:26:59 -07:00
Dockerfile Fix the build for ocid to cri-o rename 2016-09-26 16:55:12 -07:00
LICENSE Initial commit 2016-09-09 12:56:31 -07:00
Makefile Merge pull request #69 from rhatdan/master 2016-09-28 14:30:13 -07:00
OWNERS Update README with links to libraries and add OWNERS 2016-09-09 15:39:36 -07:00
README.md Add badge for Go Report Card 2016-09-28 13:52:50 -07:00

README.md

cri-o - OCI-based implementation of Kubernetes Container Runtime Interface

Build Status Go Report Card

Status: pre-alpha

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 backwards compatibility with it.

This 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:

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.

Current Roadmap

  1. Basic pod/container lifecycle, basic image pull (already works)
  2. Support for tty handling and state management
  3. Basic integration with kubelet once client side changes are ready
  4. Support for log management, networking integration using CNI, pluggable image/storage management
  5. Support for exec/attach
  6. Target fully automated kubernetes testing without failures