Let's Try Every CRI Runtime Available for Kubernetes. No, Really!
The CRI (container runtime interface) in Kubernetesdesigned to abstract the hosts runtime details from the kubelet codebasehas been around for a few years now. CRI implementations beyond the pre-ex …
| Talk Title | Let's Try Every CRI Runtime Available for Kubernetes. No, Really! |
| Speakers | Phil Estes (Distinguished Engineer & CTO, Container Architecture Strategy, IBM) |
| Conference | KubeCon + CloudNativeCon Europe |
| Conf Tag | |
| Location | Barcelona, Spain |
| Date | May 19-23, 2019 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
The CRI (container runtime interface) in Kubernetes—designed to abstract the host’s runtime details from the kubelet codebase—has been around for a few years now. CRI implementations beyond the pre-existing Docker engine driver have been appearing for some time now.As of early 2019, Docker, Virtlet, containerd, cri-o and Sylab’s Singularity project all implement the CRI! If you add in Kata containers and AWS Firecracker, the unique number of CRI combinations is growing rapidly.How would you decide which CRI implementation is right for you? Clearly each have tradeoffs that are worth understanding whether you are a developer or operator.We’ll live demo each CRI runtime and summarize the details and why a cluster might choose—or not choose—a particular runtime. It will be a fast-paced but hopefully informational talk for those looking to understand the CRI runtime landscape!
