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.

Sign up for GitHub

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

Jump to bottom

Add cri-o proposal #177

Merged
merged 8 commits into from
Apr 8, 2019
Merged

Add cri-o proposal #177

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
44c4da5
Add cri-o proposal
vbatts Nov 19, 2018
cf64f10
Update cri-o
vbatts Nov 28, 2018
2e1a2f9
Update cri-o
vbatts Nov 28, 2018
d204f42
Update cri-o
vbatts Nov 29, 2018
0ec4926
cri-o update
vbatts Dec 3, 2018
dedef9d
cri-o update
vbatts Dec 3, 2018
4abbb67
update cri-o proposal
vbatts Dec 6, 2018
755581a
Brendan Burns has agreed to sponsor
caniszczyk Mar 18, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update cri-o 
Add information on adopters.
Consistent case sizing on "cri-o"

Signed-off-by: Vincent Batts <[email protected]>
  • Loading branch information
@vbatts
vbatts committed Nov 29, 2018
commit d204f42a6a132b3f1d15584551f55077c95812c8
20 changes: 10 additions & 10 deletions proposals/cri-o.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,12 @@

*Description*:

Cri-o is a stable container runtime specifically tailored for Kubernetes.
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 and grew to production stable there.
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

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

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. 😃

This proposal is effective to promote from the kubernetes incubator a project that has fully matured.

Expand Down Expand Up @@ -62,20 +62,20 @@ Minor releases are as needed.

*Adopters*:
jonboulle marked this conversation as resolved.
Show resolved Hide resolved

* Red Hat
* Red Hat - Default container runtime for their OpenShift product
* Intel
* kata-containers
* SuSE
* Lyft
* Cillium
* kata-containers - primary CRI runtime worked with
* SuSE - Default for kubic and on track for their CaaSP offering (https://kubic.opensuse.org/blog/2018-09-17-crio-default/)
vbatts marked this conversation as resolved.
Show resolved Hide resolved
* Lyft - Default container runtime for their kubernetes deployment
* Cillium - Default example for deployment on kubernetes (https://github.com/cilium/cilium/tree/master/examples/kubernetes/)
* Nvidia
* Datica
* Datica - Default runtime for their CKS offering (https://datica.com/compliant-kubernetes-service/)

*Statement on alignment with CNCF mission*:

Cri-o's mission and goal is to align with and provide everything that Kubernetes expects from a container-runtime, and nothing more.
CRI-O's mission and goal is to align with and provide everything that Kubernetes expects from a container-runtime, and nothing more.
Based on the OpenContainer Initiative (OCI) format for container images, runtimes and distribution, with compatibility for existing docker formats as well.
The cri-o project is imbued with the spirit of Kubernetes and the CNCF mission.
The CRI-O project is imbued with the spirit of Kubernetes and the CNCF mission.

*Contributors*: https://github.com/kubernetes-sigs/cri-o/graphs/contributors

Expand Down