Unleashing WebAssembly in Kubernetes with Kwasm

Unleash the power of WebAssembly within your Kubernetes cluster using Kwasm! Combine the best of both worlds by combining WASM with Kubernetes and its ecosystem.

#WebAssembly #Kubernetes #Kwasm #WASM

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 WASM in Kubernetes
05:30 Enable WASM in Kubernetes with Kwasm Operator
07:09 Package WASM Applications as Container (OCI) Images with Fermyon Spin
09:04 Running WASM Through "Standard" Kubernetes Resources
10:39 WASM, Kwasm Pros and Cons

[rikschaaf]

The biggest advantage I see is that if you run a wasm runtime instead of a container, you get architecture independence out of the box: if there's a wasm runtime for the arch, your code will run on that arch, without having to think about which archs to support at build time. This is a pain that I'm feeling right now, as I'm setting up my ARM64-based cluster, after coming from an x86-64 based setup. A lot of official packages just don't support ARM.

[blaiseutube]

K8s is meant to be a toolkit for building orchestration tools.
Kwasm is the Way.

[ParkerLouisDE]

Never used a RuntimeClass or WASM yet. Now it makes sense. Thanks Viktor!

[IvanRizzante]

Thanks for another great video! I like the idea behind WASM but there is no drop in replacment or magic formula to make your application run in WASM straightaway. There are changes to make and they may be many depending on the size of your projects. Let's not forget that some WASM implementations for popular languages like Java may not support all the features you need (at least not at the moment). I see security and speed as the 2 major advantages in using WASM but I also know that containers in Kubernetes, when done right and with the help of policies, offer comparable security levels and are isolated too through Linux namespaces. About speed one would ideally need to try its own apps in WASM and containers to tell the difference. All in all switching to WASM would still depends on many things, if your needs justify the effort then maybe it's worth it especially considering tools like Kwasm that could simplify placing your apps in Kubernetes.

[Jaabaa_Prime]

Hi Viktor, I think you missed one of **THE** major advantages, WASM is platform independent. The Runtime is platform dependent not while building the container image!

[JoaoFerreira-nrcc]

Please, why it does not work on Oracle OKE? (as you said at 12:42)

[martinbower]

I'm off to play, I'm interested in the start up times, speed of scaling up and down.
Thanks for the video !

[gackerman]

didn't realize there was so little I knew about WASM and its capabilities...

[gunnarsinn]

can I schedule spin and traditional runc containers BOTH on an annotated node or does it break runc?

[andrewdatar]

Awesome video, thank you! Please update "Transcript and commands" link, currently it goes to the page about Justfile

I wonder how it would run on RKE2 or K3S. As usual thanks for the great content Viktor!

[chrisalexthomas]

So would you say that this basically allows serverless computing on kubernetes without all of those extra frameworks like kubeless or knative?

[tehseensajjad]

What about the network namespacing and ephemeral storage for the wasm "pod"?

is the wasm binary namespaced?

[masoudbaharlouie]

Was it by accident that wasmCloud - a CNCF project - missed? It does have a k8s operator, and is architected to stretch across servers and cloud platforms, with or without k8s (thanks to use of NATS as the underlying bus).

[slim]

This is really a missing link for wasm adoption. It would seem that wasm apps are becoming viable.
But is it even possible to package large projects as wasm binaries?

[Sebastian-orxw]

Kwasm sadly looks like it's dead. Not much activity since at least December 2023