vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
No description
185 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
Antonio Murdaca aebd365cf4
test: tweak halpers 
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
2016-09-24 00:38:06 +02:00
.tool cmd/client: split commands in multiple files 2016-09-24 00:31:46 +02:00
cmd cmd/server: provide a flag to set ocid root dir 2016-09-24 00:38:06 +02:00
conmon conmon: use runtime path from ocid 2016-09-17 11:37:45 +02:00
hack hack/vendor.sh: fix script 2016-09-24 00:37:09 +02:00
oci id and name indexes for pods 2016-09-22 18:17:45 +02:00
server cmd/server: provide a flag to set ocid root dir 2016-09-24 00:38:06 +02:00
test test: tweak halpers 2016-09-24 00:38:06 +02:00
testdata Add an example config to demonstrate container exit 2016-09-19 15:30:28 -07:00
utils Convert status to exit code 2016-09-19 12:25:13 -07:00
vendor/src vendor to ./vendor/src 2016-09-24 00:37:09 +02:00
.gitignore add tests skeleton 2016-09-24 00:37:07 +02:00
.travis.yml makefile stuff 2016-09-19 19:51:03 +02: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 add tests skeleton 2016-09-24 00:37:07 +02:00
LICENSE Initial commit 2016-09-09 12:56:31 -07:00
Makefile add tests skeleton 2016-09-24 00:37:07 +02:00
OWNERS Update README with links to libraries and add OWNERS 2016-09-09 15:39:36 -07:00
README.md adding current roadmap 2016-09-23 14:48:39 -07:00

README.md

OCID - OCI-based implementation of Kubernetes Container Runtime Interface Build Status

Status: pre-alpha

What is the scope of this project?

OCID 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 OCID is tied to the scope of the CRI.

At a high level, we expect the scope of OCID 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 OCID. 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