Evaluating Firecracker as a container runtime engine
05-18, 11:35–12:05 (UTC), Main Hall

I will explain the overview of the architecture around Firecracker and container runtimes. Then I will show demos for a proof-of-concept implementation.


Firecracker, an open-source project published by Amazon, opens up a lot of interesting perspective to the container ecosystem. It opens up use cases between containers and VMs, making use of KVM without relying on heavyweight Qemu instances. Its integration with the Kubernetes ecosystem has only started its first step with containerd. Obviously it’s a good starting point. However, it's also time to think about how we should get the new shape of containers integrated with all other high-level container runtimes.

In this talk, I would like to talk about alternative ways of integration for getting Firecracker integrated with multiple container runtimes. A proof-of-concept implementation will be also presented during the talk.

From the side of Firecracker, its integration with the Kubernetes ecosystem has only started its first steps, only with containerd & Kata containers. For the diversity of Kubernetes ecosystem, however, we should also think about how we should get Firecracker integrated with all other high-level container runtimes in the cloud-native ecosystem.

Software Engineer at Kinvolk
Active mainly on open source projects like kube-spawn or Flatcar Linux.
Github: https://github.com/dongsupark