From 39d37f2b8f475c482cbf23d36cbb0d4b921fdb96 Mon Sep 17 00:00:00 2001 From: Mrunal Patel Date: Sat, 26 Aug 2017 16:31:20 -0700 Subject: [PATCH] readme: Link to CRI documentation and update status to beta Signed-off-by: Mrunal Patel --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8e6a6844..dd962141 100644 --- a/README.md +++ b/README.md @@ -4,12 +4,12 @@ [![Build Status](https://img.shields.io/travis/kubernetes-incubator/cri-o.svg?maxAge=2592000&style=flat-square)](https://travis-ci.org/kubernetes-incubator/cri-o) [![Go Report Card](https://goreportcard.com/badge/github.com/kubernetes-incubator/cri-o?style=flat-square)](https://goreportcard.com/report/github.com/kubernetes-incubator/cri-o) -### Status: alpha +### Status: beta ## 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. +Specifically, it implements the Kubelet [Container Runtime Interface (CRI)](https://github.com/kubernetes/community/blob/master/contributors/devel/container-runtime-interface.md) 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: