- [VOTE] CRI-O project proposal (incubation)
Re: [VOTE] CRI-O project proposal (incubation)
toggle quoted messageShow quoted text
On Tue, Mar 19, 2019 at 9:21 AM Erin Boyd <eboyd@...
On Tue, Mar 19, 2019 at 1:57 PM Chris Aniszczyk <caniszczyk@...
The CRI-O project is being proposed as an INCUBATION level CNCF project, sponsored by Brendan Burns from the TOC: https://github.com/kubernetes-sigs/cri-o
CRI-O is a stable container runtime specifically tailored for Kubernetes. A founding principal was not "reinventing the wheel" and so the project uses shared components, refined approaches tested in production, and existing battle-tested code. Further, it is tuned for performance, stability, compatibility, and adherence to standards, particularly the Kubernetes Conformance tests. In short CRI-O is a building block of a Kubernetes cluster, to facilitate the life cycle of containers as required by the Kubernetes Container-Runtime-Interface (CRI).
CRI-O was born in kubernetes-incubator (which is now deprecated) and grew to production stable there. Some have claimed since being a kubernetes project that it is already "a CNCF project", but it is often left as an after thought in brand, awareness and support as a top-level project. This proposal is effective to promote from the kubernetes incubator a project that has fully matured.
Moving CRI-O is consistent with both the Kubernetes project direction (see helm https://github.com/cncf/toc/pull/114
, for example) and with other container runtimes. The containerd CRI implementation moved from the Kubernetes project to the containerd project.
Please vote (+1/0/-1) by replying to this thread; the full project proposal located here: https://github.com/cncf/toc/pull/177
Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!
Chris Aniszczyk (@cra) | +1-512-961-6719
Join email@example.com to automatically receive all group messages.