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)
- Fast Track to Chaos Engineering with Russ Miles (in London on 1st - 3rd July 2019)
- Advanced Docker for Enterprise Operations (in London on 23rd - 24th September 2019)
- ProgNET London 2019 (in London on 11th - 13th September 2019)
- Keynote by Kris Nova on The Power of Linux Virtualization with Cloud Native (in London on 19th June 2019)
- The wonders of IBM: Watson, artificial intelligence, Swift coding and databases! (in London on 19th June 2019)
- Securing microservices in a serverless world (SkillsCast recorded in June 2019)
- Observability for Microservices: practical advice (SkillsCast recorded in June 2019)
Whose Job Is It!? How Kubernetes and Container Runtimes Work Together to Run Your Workloads
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.