CRI-O is a new Kubernetes runtime for running containers in a cluster. It aims at replacing Docker and it's set to be the default runtime when running OpenShift. How is this new runtime being developed? How is it making sure that nothing breaks with each release? How is stability maintained during the project development? In this talk, Antonio goes through the development behind the CRI-O project and he will walk through his team's experience over the last 2 years of developing this new runtime. He'll cover the flow of every feature, bug, and test, how the team deals with testing and its infrastructure, how CRI-O is helping the Kubernetes project by helping fixing issues that arise during CRI-O development and future improvements already planned to make CRI-O always ready for Kubernetes.
