Red Hat and SUSE on CRI-O
-
Red Hat contributes CRI-O to the Cloud Native Computing Foundation
Today CRI-O, a project started at Red Hat in 2016 to be an Open Container Initiative-based implementation of the Kubernetes Container Runtime Interface, is being contributed to the Cloud Native Computing Foundation (CNCF). This project joins cornerstone containers and Kubernetes projects we’ve been a part of like etcd and others to join a neutral home for stewardship.
This is a step forward for the containers and CRI-O community because it brings the project into the same home as Kubernetes, which benefits users given its close interdependency. CRI-O and Kubernetes follow the same release cycle and deprecation policy.
CRI-O already has a variety of maintainers outside of Red Hat including Intel and SUSE. Red Hat plans to continue participating in developing CRI-O, especially as a part of our enterprise Kubernetes product, Red Hat OpenShift. With our heritage and dedication to open source software and community-driven development, CRI-O can benefit the community even further within CNCF housed next to Kubernetes.
-
Welcome to the CNCF, CRI-O!
CRI-O, the Open Container Initiative (OCI) implementation of the Kubernetes Container Runtime Interface (CRI), will join the Cloud Native Computing Foundation (CNCF) incubator today. The project provides an alternative container runtime for Kubernetes and was founded back in 2016 (originally known as OCID) with the introduction of the Kubernetes CRI. CRI-O focuses on its first principles of stability and reliability. This has been proven since one and a half year for now and CRI-O synchronizes its releases with Kubernetes to ensure these principles for the future, too. The projects popularity raised over the past years that it is now the best solution to run Kubernetes workloads in a secure fashion. Currently, CRI-O has worldwide 106 contributors and 9 maintainers coming from Intel, Red Hat, and SUSE. SUSE CaaS Platform version 3 provides it as a technology preview, where CRI-O can be chosen during the installation. No further workload changes are needed to switch from Docker or containerd to CRI-O.
- Login or register to post comments
- Printer-friendly version
- 2469 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
Cloud Native Computing Foundation adopts Kubernetes-friendly...
Cloud Native Computing Foundation adopts Kubernetes-friendly container runtime