WebAssembly is coming to Cloud Native
Is the title of this post a pun inspired by Christmas or by the Games of Thrones?
I can’t decide…
Are my dad jokes as bad as my daughters claim? Probably…
Is WebAssembly spreading inside of the Cloud Native ecosystem? 💯 I have no doubts about that!
First of all, why am I so excited about seeing WebAssembly flourish inside of the Cloud Native ecosystem? Well, it’s no secret that I’m a huge fan of it. After all, WebAssembly is at the heart of Kubewarden.
WebAssembly is flexible. It grants Kubewarden policy authors the freedom to pick their favorite languages and tools to write policies. WebAssembly allows developers to tap into the huge ecosystem of programming languages such as Rust, Go and many others to produce portable “build once, run everywhere” units of code.
WebAssembly is interoperable. This opens interesting scenarios to Kubewarden operators, too. Did you know that Rego-based policies, such as Open Policy Agent and Gatekeeper, can be built as WebAssembly modules? We are currently working on a way to run Rego-based policies on top of Kubewarden. This will allow operators to have a single policy platform to operate. We will talk more about that in a future post – stay tuned for updates!
WebAssembly is secure. It has been designed with a strong focus on security since the beginning. Each WebAssembly module runs inside a dedicated sandbox, with no access to other WebAssembly processes or the host system. Kubewarden is a project operating in the security space, making it even more important to ensure our policies cannot be turned into an attack vector.
Thankfully, WebAssembly and its runtime already do the heavy lifting for us.
So, I kept talking about WebAssembly and how much I love it. I gave you
some reasons, but I didn’t dig into the details. Luckily,
The New Stack has recently published not one, but
two articles featuring WebAssembly.
These articles do a great job at explaining why everybody keeps talking about WebAssembly and how WebAssembly can even change some computing assumptions.
Take some time and give them a read. I’m sure you will find them interesting. Plus, cherry on top, they both feature Kubewarden 😊.
But we’re not over yet; more exciting things happened this week. The following projects started the process to get included in the CNCF sandbox: Krustlet (see here), wasmCloud (see here) and ORAS (see here).
Let’s take a closer look at them!
Krustlet registers itself against a Kubernetes cluster as a Kubelet instance. However, the Krustlet Kubelet does not run regular containers; it instead executes WebAssembly programs.
Krustlet leverages OCI registries to distribute the WebAssembly modules to execute. This is the same approach Kubewarden adopts to distribute its policies.
As a matter of fact, the Krustlet and Kubewarden teams are collaborating on the oci-distribution crate. This is the Rust library that Krustlet and Kubewarden use to retrieve Wasm modules from OCI registries.
wasmCloud is a project with a strong focus on the developer experience. wasmCloud provides a way to write portable code, that can be deployed everywhere: from the cloud to your edge devices. As the name of the project suggests, wasmCloud leverages WebAssembly too.
Once more, as Kubewarden developers we are connected to the wasmCloud community, too. Both Kubewarden and wasmCloud are contributors to the waPC project. This is the glue that allows our WebAssembly guest code to interact with the host.
On the surface this project doesn’t seem to be related to WebAssembly. However, without ORAS, neither Krustlet nor Kubewarden could store WebAssembly modules inside of OCI Container registries.
On behalf of the Kubewarden developers, let me congratulate all the teams behind these projects. Thanks for inspiring us and paving the way for WebAssembly inside of CNCF!
Who knows, hopefully, Kubewarden will join your ranks one day! 🤓