Distribute WebAssembly modules as OCI artifacts

Tue, 02 Nov 2021 14:19:39 +0000

When using WebAssembly (Wasm) on platforms different than the browser, we have to care about distribution. How can we securely transfer our Wasm modules to desired environments? How can we verify integrity to ensure Wasm modules were not compromised during distribution?

Let’s take a look at the container world. Container registries (those that implement the Docker Registry 2.0 standard (or to be more precise, the OCI distribution spec )) are a trusted distribution channel that addresses all the questions raised before. This does not mean that we have to package our Wasm modules as containers! Container registries can store and distribute more than just containers. Container registries can store any OCI compliant artifact. And that’s exactly what we will create from our Wasm modules to leverage container registries as a trusted distribution channel.

Add krustlet node pools to Azure Kubernetes Service

Tue, 26 Oct 2021 14:23:42 +0000

If we had traveled three years back in time, running WebAssembly (Wasm) workloads in Kubernetes would have sounded like fiction. Today, it’s real! With krustlet , developers can run Wasm workloads directly in Kubernetes. This article will look at what krustlet is and how we can bring it to our Azure Kubernetes Service (AKS) clusters.

What is Krustlet

Krustlet is a Kubernetes kubelet written in Rust to run Wasm workloads in Kubernetes. Nodes running krustlet have special tolerations assigned, which we can use within Kubernetes manifests, to ensure Wasm workloads will be scheduled to krustlet nodes. Under the covers, krustlet uses wasmtime as the runtime for our Wasm workloads using the wasm32-wasi architecture.

Wasm on Thorsten Hans

Distribute WebAssembly modules as OCI artifacts

Add krustlet node pools to Azure Kubernetes Service

What is Krustlet