 So I'm much mid working as a consultant at liquid reply And I will give you a little showcase today About our K wasm operator that we created which provides you an easy way for running your web assembly workloads in your Kubernetes clusters So what K wasm actually is doing It provides you a way for your local clusters for example that you created with kind mini-cube micro-cuban at this or Colima To a run your web assembly workloads and it also works on managed services like Azure AKS the Google Kubernetes engine AWS EKS or basically any provider But so there are some limitations as you can see in this table for example for minicube and Colima It's required that Contina DS used and as you can also see the Yellow arrows for GCP and AWS When you create your cluster You need to configure your notes or like the cluster to be running Ubuntu and container D So it will only work with Ubuntu nodes for these cloud providers And now to get a little bit into more detail on how it actually works and what this is doing So on the left side you can see the diagram So you have your notes in your cluster and you create an annotation on these notes So you annotate the note This will be picked up by our operator And once the operator sees a note with a specific annotation It will create a job in your cluster That the job you can actually see here on the on the right side So this job is then in charge with our KWASM node installer image that we created To provision this annotated note And this is working with a patched CRUN That is being installed on your note directly with WebAssembly support In the case of a spin the container DSHIM spin will be used So now let's jump into a quick demo Which is actually not live So the first thing that you would do when you have your node provisioned by the operator is That you create a runtime class with the CRUN handler in this demo And then we would create a pod This is just an example pod using the example of Vazi image So we can actually get some output and you can see that we have an annotation for this Kubernetes pod Which executes With sorry which tells CRUN how to execute the container This is the compact smart annotation that you see on the screenshot And if we go a little bit to the bottom You see a node selector Because the annotation you can see the KWASM provisioned annotation is actually created on the Already provisioned node by the operator So that the pod will really only get scheduled or nodes in your cluster that are enabled for WebAssembly support because you may have multiple nodes and you don't want every node to Schedule your WebAssembly and workloads and at the very bottom of Of the pod you can see the one-time class that we just created so this needs to be specified the CRUN class Of course in this demo now there's no operator installed so you can see that it's not being scheduled Because there's no provisioned node what we will do now is We will install the operator using our ham chart that we created So you would add the ham repository if you want to check this out locally Then you will install our ham chart into your cluster and then at the very last line We will actually do with the annotation that I talked about so we will annotate the node with KWASM as H slash KWASM node equals true and Then the operator will deploy the provisional job into the cluster which Will then enable the node for WebAssembly support and Once this is done if we now go back to the same pod that previously was not scheduled We will see that it was scheduled and when we would check the logs for this part we will see That that's like the default output of the was a sample container And that's it for the KWASM operator Thank you very much. This was actually my first talk I ever had so it's Kind of excited If you have any more questions to this I want to get a live demo and we have a booth here at the kubecon I will be very happy to to show you this in a little bit more detail If you want to check it out yourself, you can visit kwasm.sh We provide getting started instructions for different providers Or you can also contact us directly at liquidreply.com Thank You very much, Maas We have time for one or two questions There are no questions. I do have some questions. I don't know if you can compare these to some of the other Efforts in in the space how it relates to rune wasi or some of the products that came before What are their interesting projects you see in the space bridging Kubernetes and WebAssembly? I Actually can't really give you an answer to this. I'm not a WebAssembly expert. I really just created this operator so I'm not really that much involved in WebAssembly itself, but it's really Yeah, just really just creating this operator to Yeah, so and actually my colleague seems like maybe has more answer because he's the WebAssembly Professional, so maybe he can say something Thank you for the question regarding that it actually leverages rune wasi, so it's not a runtime itself It's an installer and it uses the WebAssembly Runtimes that are around and also different image formats. So on Thursday, we will have at 11 at our booth a short demo of the not yet released Wasm worker server one wasi shim together with Angel, so If you want to come so we have a demo. Thank you so much. I'm looking forward to that Any other questions? Okay, thank you. Please give a runoff applause to max