[VOTE] CRI-O project proposal (incubation)


Chris Aniszczyk
 

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


Randy Abernethy
 

+1 nb


On Tue, Mar 19, 2019, 06:57 Chris Aniszczyk <caniszczyk@...> wrote:
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


Chris Short
 

+1 non-binding

💯

On Tue, Mar 19, 2019 at 09:57 Chris Aniszczyk <caniszczyk@...> wrote:
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

--

Chris Short


Davanum Srinivas
 

+1 (Non-binding)

On Tue, Mar 19, 2019 at 7:47 PM Chris Short via Lists.Cncf.Io <chris=chrisshort.net@...> wrote:
+1 non-binding

💯

On Tue, Mar 19, 2019 at 09:57 Chris Aniszczyk <caniszczyk@...> wrote:
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

--

Chris Short



--
Davanum Srinivas :: https://twitter.com/dims


Matt Klein
 

+1 binding

On Tue, Mar 19, 2019 at 6:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
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


alexis richardson
 

+1 binding

On Tue, Mar 19, 2019 at 3:03 PM Matt Klein <mattklein123@...> wrote:
+1 binding

On Tue, Mar 19, 2019 at 6:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
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


Brian Grant
 

+1 binding

On Tue, Mar 19, 2019 at 8:06 AM alexis richardson <alexis@...> wrote:
+1 binding

On Tue, Mar 19, 2019 at 3:03 PM Matt Klein <mattklein123@...> wrote:
+1 binding

On Tue, Mar 19, 2019 at 6:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
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


Joe Beda <jbeda@...>
 

+1 binding

 

From: <cncf-toc@...> on behalf of "Brian Grant via Lists.Cncf.Io" <briangrant=google.com@...>
Reply-To: "briangrant@..." <briangrant@...>
Date: Tuesday, March 19, 2019 at 8:19 AM
To: alexis richardson <alexis@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 binding

 

On Tue, Mar 19, 2019 at 8:06 AM alexis richardson <alexis@...> wrote:

+1 binding

 

On Tue, Mar 19, 2019 at 3:03 PM Matt Klein <mattklein123@...> wrote:

+1 binding

 

On Tue, Mar 19, 2019 at 6:57 AM Chris Aniszczyk <caniszczyk@...> wrote:

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


Michelle Noorali
 

+1 binding


From: cncf-toc@... <cncf-toc@...> on behalf of via Lists.Cncf.Io <jbeda=vmware.com@...>
Sent: Tuesday, March 19, 2019 11:25 AM
To: briangrant@...; alexis richardson
Cc: cncf-toc@...
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)
 

+1 binding

 

From: <cncf-toc@...> on behalf of "Brian Grant via Lists.Cncf.Io" <briangrant=google.com@...>
Reply-To: "briangrant@..." <briangrant@...>
Date: Tuesday, March 19, 2019 at 8:19 AM
To: alexis richardson <alexis@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 binding

 

On Tue, Mar 19, 2019 at 8:06 AM alexis richardson <alexis@...> wrote:

+1 binding

 

On Tue, Mar 19, 2019 at 3:03 PM Matt Klein <mattklein123@...> wrote:

+1 binding

 

On Tue, Mar 19, 2019 at 6:57 AM Chris Aniszczyk <caniszczyk@...> wrote:

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


Erin Boyd
 

+1 (non-binding)

On Tue, Mar 19, 2019 at 1:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
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


Gilbert Song
 

+1 (non-binding)

On Tue, Mar 19, 2019 at 9:21 AM Erin Boyd <eboyd@...> wrote:
+1 (non-binding)

On Tue, Mar 19, 2019 at 1:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
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


Ihor Dvoretskyi
 

+1 (non-binding). 


On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
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


Yassine Tijani <ytijani@...>
 

+1 nb


Le mar. 19 mars 2019 à 14:57, Chris Aniszczyk <caniszczyk@...> a écrit :
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


Sonya Koptyev <sonya@...>
 

+1 non-binding

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism
m: +1 425 505 0100



On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:
+1 (non-binding). 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:
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


Li, Xiang
 

+1 binding


Nick Chase
 

+1 non-binding

On Tue, Mar 19, 2019 at 6:15 PM "Li, Xiang <x.li@...> wrote:
+1 binding


iftach Schonbaum
 

+1 non-binding

 

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

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


Pengfei Ni
 


+1 non-binding



Best regards.


---
Pengfei Ni



iftach Schonbaum <iftachsc@...> 于2019年3月20日周三 下午2:41写道:

+1 non-binding

 

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

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


Marius Grigoriu
 

+1 non-binding

 

From: <cncf-toc@...> on behalf of Pengfei Ni <feiskyer@...>
Date: Wednesday, March 20, 2019 at 6:04 AM
To: iftach Schonbaum <iftachsc@...>
Cc: "sonya@..." <sonya@...>, Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>, "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 


+1 non-binding

 

 

Best regards.

 

 

---

Pengfei Ni

 

 

 

iftach Schonbaum <iftachsc@...> 2019320日周三 下午2:41写道:

+1 non-binding

 

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

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


Thomas Mclennan
 

+1 non-binding

On Mar 20, 2019, at 8:48 AM, Grigoriu, Marius via Lists.Cncf.Io <marius.grigoriu=nordstrom.com@...> wrote:

+1 non-binding

 

From: <cncf-toc@...> on behalf of Pengfei Ni <feiskyer@...>
Date: Wednesday, March 20, 2019 at 6:04 AM
To: iftach Schonbaum <iftachsc@...>
Cc: "sonya@..." <sonya@...>, Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>, "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 


+1 non-binding

 

 

Best regards.

 

 

---

Pengfei Ni

 

 

 

iftach Schonbaum <iftachsc@...> 2019320日周三 下午2:41写道:

+1 non-binding

 

 

<image001.gif>

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

<image002.jpg>

<image003.png>

 

 

 

From: <cncf-toc@...> on behalf of "Sonya Koptyev via Lists.Cncf.Io" <sonya=twistlock.com@...>
Reply-To: "sonya@..." <sonya@...>
Date: Tuesday, 19 March 2019 at 22:26
To: Chris Aniszczyk <caniszczyk@...>, Ihor Dvoretskyi <ihor.dvoretskyi@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CRI-O project proposal (incubation)

 

+1 non-binding

 

Thanks,
Sonya

Sonya Koptyev | Director of Product Marketing and Evangelism

m: +1 425 505 0100

 

<image004.png>

 

On Mar 19, 2019, 1:25 PM -0700, Ihor Dvoretskyi <ihor.dvoretskyi@...>, wrote:

+1 (non-binding). 

 

On Tue, Mar 19, 2019, 3:57 PM Chris Aniszczyk <caniszczyk@...> wrote:

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