Announcing CRI-O v1.0.2

I’m pleased to announce that we’ve just released the new CRI-O v1.0.2. This is a minor release of the v1.0.x cycle supporting Kubernetes 1.7.

This minor release isn’t adding any new feature. We focused on stability, performance and general bug fixing. For a detailed list of all the changes between v1.0.1 and v1.0.2 you can read more at the GitHub release page.

Most importantly, we fixed a bug in the interaction between CRI-O and kubeadm/kube-proxy and a memory leak in how we were setting up the info endpoint used by cAdvisor in Kubernetes.

CRI-O follows the first rule of the original Unix philosophy:

Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new “features”.

By focusing on Kubernetes and the CRI we have a small code base and small separate components so we’re able to fix bugs and audit the code pretty rapidly. Performance benefits by this as well and we’ve worked hard to ensure CRI-O performs really well.

Packages should be available for Fedora/Ubuntu/CentOS shortly. Please test the new version and send feedback or suggestions. Don’t be shy. Reach out to us on Github, Freenode #cri-o, or directly tweet me :)
Grazie mille!