Understanding Wasm on Kubernetes
This section introduces the major requirements for running Wasm apps on Kubernetes clusters that use containerd. Other ways to run Wasm apps on Kubernetes exist.
This is also just an overview section. We’ll cover everything in more detail in the hands-on section.
It’s widely understood that Kubernetes is a high-level orchestrator that uses other tools to perform low-level tasks such as creating, starting, and stopping containers. The most common configuration is Kubernetes using containerd to manage these lower-level tasks.
Figure 9.2 shows Kubernetes scheduling tasks to a worker node running containerd. containerd instructs runc to build the container and start the app. After the container is created, runc exits, and the shim process maintains the connection between the running container and containerd.
In this architecture, everything below containerd is hidden from Kubernetes. This makes it possible...