Whose Job Is It!? How Kubernetes and Container Runtimes Work Together to Run Your Workloads
With the move from the common-place Docker-based executor for Kubernetes pods to the Container Runtime Interface (CRI), the definition of the contract between container runtime and Kubernetes pod has gotten much clearer in the past year. Given the CRI is somewhat new, in this talk we'll explore what the CRI is and how container runtimes implement the CRI API to offer container execution to Kubernetes.
In addition, we'll look at how the CNCF containerd 1.0 release and the associated containerd CRI project are building a stable and performant core container execution environment for Kubernetes. We'll demonstrate how to use these CNCF projects together and do a quick demo of Kubernetes 1.9 running with containerd 1.0.1.
YOU MAY ALSO LIKE:
- Container Security (SkillsCast recorded in July 2016)
- Docker Fundamentals with Matt Saunders (Online Course on 22nd - 25th February 2021)
- Advanced Kubernetes Concepts with Jérôme Petazzoni (Online Course on 22nd - 25th March 2021)
- Introducing AWS Immersion Days (Online Meetup on 11th February 2021)
- Event-Driven Microservices: The Sense, Nonsense and a Way Forward (SkillsCast recorded in December 2020)
- Lightning Talk: E Pluribus Unum – Adventures in Polycloud Delivery (SkillsCast recorded in December 2020)
Thank you to our sponsors and partners
Platinum
Whose Job Is It!? How Kubernetes and Container Runtimes Work Together to Run Your Workloads
Phil Estes
Phil is a Senior Technical Staff Member in the office of the CTO of IBM Cloud Platform. Phil is a core contributor and maintainer on the Docker engine project where he has contributed key features like user namespace support and multi-platform image capabilities. Phil is also a founding maintainer of the CNCF containerd project, and participates in the Open Container Initiative (OCI) as a contributor to the development of runc.