Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add cri-o proposal #177

Merged
merged 8 commits into from Apr 8, 2019
Merged

Add cri-o proposal #177

merged 8 commits into from Apr 8, 2019

Conversation

vbatts
Copy link
Contributor

@vbatts vbatts commented Nov 28, 2018

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
@caniszczyk caniszczyk added this to In progress (due diligence) in TOC Project Backlog Nov 28, 2018
vbatts added 2 commits Nov 28, 2018
Description tweaks

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
Datica https://datica.com/compliant-kubernetes-service/

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
proposals/cri-o.adoc Show resolved Hide resolved
proposals/cri-o.adoc Outdated Show resolved Hide resolved
proposals/cri-o.adoc Outdated Show resolved Hide resolved
@vbatts
Copy link
Contributor Author

vbatts commented Nov 29, 2018

@vbatts
Copy link
Contributor Author

vbatts commented Nov 29, 2018

Add information on adopters.
Consistent case sizing on "cri-o"

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
@vbatts
Copy link
Contributor Author

vbatts commented Nov 29, 2018

I have been pinged by a few folks about whether this proposal could be related to decisions about rkt as a CNCF project. That is a fine point, but should be a distinct conversation to be had separate from this proposal.

proposals/cri-o.adoc Outdated Show resolved Hide resolved
proposals/cri-o.adoc Outdated Show resolved Hide resolved
proposals/cri-o.adoc Outdated Show resolved Hide resolved
vbatts added 3 commits Dec 3, 2018
removed LGPLv3 dep from list
cri-o/cri-o#1936

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
SUSE casing and links

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
finally got the https:// fixed for cri-o.io

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
@vbatts
Copy link
Contributor Author

vbatts commented Dec 6, 2018

all current points addressed. PTAL

- sameo
- rhatdan
- nalind
- giuseppe
Copy link
Contributor

@mattfarina mattfarina Jan 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For those wondering, initial committers is made up of people from Red Hat, Suse, Intel, and IBM.

Instead of Initial Committers should these be labeled Maintainers?

Copy link
Contributor Author

@vbatts vbatts Jan 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's a fine suggestion. I was mimicking prior proposals, but they would be initial maintainers.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does CNCF have distinct definitions for Committers and Maintainers?

* #cri-o on Freenode IRC
* https://kubernetes.slack.com/messages/crio

*Website*: https://cri-o.io
Copy link
Contributor

@mattfarina mattfarina Jan 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed on the website the branding says:

Lightweight Container Runtime for Kubernetes

Would the change to the CNCF also be shifting it from one "for Kubernertes" to one that others can use for other purposes as well?

Copy link
Contributor Author

@vbatts vbatts Jan 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if those other use cases only conform to the kubernetes CRI, then maybe but numero uno is k8s. 😄

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 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.
Copy link
Contributor

@mattfarina mattfarina Jan 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is it you want the brand and awareness to go? Is there some form of support you are looking for as a top level project?

For example, when Helm shifted out of Kubernetes there was a need for help organizing Helm conferences (currently prepping for a second) and it had many contributors (it's the 3rd most contributed to CNCF project) where support for scaling that was needed.

Is cri-o looking to be more than a container runtime for k8s? Is there something else going on?

I ask these questions as I'm curios to understand more of where cri-o is going.

Copy link
Contributor Author

@vbatts vbatts Jan 22, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm glad that kubernetes-incubator was renamed kubernetes-sigs, but cri-o has outgrown that level of incubation.
And truthfully due to not getting the same level of press as containerd or rkt, I get feedback that folks infer it is not considered on the same level.
No cri-o conferences needed. 😃

@mattfarina
Copy link
Contributor

mattfarina commented Jan 15, 2019

FWIW, containerd and rkt are both "container runtimes" in the CNCF. Another example of similar things is etcd and TiKV as key/value stores. There doesn't appear to be a criteria that only one project of a type be in the CNCF.

@caniszczyk
Copy link
Contributor

caniszczyk commented Jan 17, 2019

@vbatts
Copy link
Contributor Author

vbatts commented Feb 28, 2019

What is the next step here?

@caniszczyk
Copy link
Contributor

caniszczyk commented Feb 28, 2019

@umohnani8 umohnani8 mentioned this pull request Mar 4, 2019
@caniszczyk caniszczyk moved this from In progress (due diligence) to TOC Approved (sponsors/voting) in TOC Project Backlog Mar 19, 2019
@rothgar
Copy link
Member

rothgar commented Mar 19, 2019

I'm sorry I haven't kept up with CRI-O so some of these questions may be answered elsewhere but I didn't see them explicitly called out in this proposal.

What's the state of CRI-O's support in k8s? Last I looked at it it was an alpha release not supported in k8s yet.
Are there production users or hosted k8s that use CRI-O?

@vbatts
Copy link
Contributor Author

vbatts commented Mar 20, 2019

@rothgar hey hey, CRI-O has been out of alpha since Oct 2017 which was around k8s v1.7, then with k8s v1.8 CRI-O began it's release versioning to match kubernetes.

We've have production users (besides Red Hat internal) since before CRI-O was v1.0. Today there are a number of large scale down to smaller shops. Not all want to be publicly listed, which we respect.

@caniszczyk
Copy link
Contributor

caniszczyk commented Apr 8, 2019

@caniszczyk caniszczyk merged commit e3e4cf6 into cncf:master Apr 8, 2019
@caniszczyk caniszczyk moved this from TOC Approved (sponsors/voting) to Done in TOC Project Backlog Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet