With the introduction of the Kubernetes Container Runtime Interface (CRI), many different choices have emerged for users to run their various containerized workloads. At the same time, the development community has been gradually directing more of its attention toward running untrusted serverless or single container workloads than on running and securing infrastructure.
Ricardo Aravena showcases some of the newer container runtimes, including Kata Containers, Nabla Containers, and gVisor, and explains how to use them to isolate workloads in an effortless way. You’ll learn how the different container communities are working together with the Kubernetes project to identify the unique capabilities of each containerized approach and discover how they relate with two newer enhancements: the Kubernetes Runtime Class to run multiple runtimes in a single Kubernetes cluster and Firecracker microVMs, a new open source project from AWS that makes it possible to spin up thousands of lightweight sandboxed virtual machines.
Ricardo Aravena is an infrastructure manager at Rakuten, helping automate everything in containers using open source and lately contributing to the Kata Containers project. He’s been working in tech for more than 19 years and comes from a diverse professional background, including roles at large companies such as Cisco and VMware as well as startups such as Coupa, Hytrust, Exablox, and SnapLogic. Most recently he he spent two years at Branch Metrics working on automating the company’s cloud infrastructure to handle millions of requests and petabytes of data on a daily basis.
For exhibition and sponsorship opportunities, email firstname.lastname@example.org
For information on trade opportunities with O'Reilly conferences, email email@example.com
View a complete list of Velocity contacts
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org