krustlet
krustlet copied to clipboard
krustlet
What is the status of this project?
Hi guys, first of all I think this project is amazing and that's why I would like to know what the status of this project is and if you intend to keep it in the long term.
I would join the question. Is there any road map available? I'm using Kubernetes at low cost, non-profit scale, hope to move some workloads to Krustlet in the future, contribute to few projects to port to WebAssembly 😄
EDIT: Found the Roadmap on the blog https://deislabs.io/posts/towards-krustlet-v1-cncf/ sounds cool!
EDIT: Found the Roadmap on the blog https://deislabs.io/posts/towards-krustlet-v1-cncf/ sounds cool!
The Post was in July of last year and since then nothing else has happened, no one responds to issues or questions, an excellent project but without feedback it is difficult to use
Hi @sleipnir. What brought your interest in Krustlet? Is there a particular scenario that you wanted to use the project?
Some members of the Azure team are working on krustlet-adjacent projects like runwasi - a project very similar to an older experiment of Krustlet called wok. If you wanted the krustlet binary for integration into Kubernetes, there are other supported solutions available (like runwasi) with an active group of maintainers. Please take a look at that, because it might be better suited for your use case. On the other hand, if you wanted to use krustlet for its kubelet crate and state engine crate in Rust, it's still there and is maintained in the sense that there are contributors around to help, but might be delayed on tagging, so definitely reach out on the slack channel for help.
On a more personal note, some of the original team working on the Krustlet project (including myself) have changed employers and moved onto other projects. Some joined Fermyon Technologies. Others joined wasmCloud. Most of us are actively contributing to the oci-distribution crate for other wasm-related work, but we haven't contributed code to krustlet/krustlet in a while as noted above.
If you have any further questions about the status of this project, please feel free to reach out to @squillace.
Hi @bacongobbler, thanks for replying. My main interest is to add support for Lunatics on Krustlet to be able to use it in workloads managed by Kubernetes.
Meanwhile, Microsoft has made this Preview available:
https://docs.microsoft.com/en-au/azure/aks/use-wasi-node-pools
Meanwhile, Microsoft has made this Preview available:
https://docs.microsoft.com/en-au/azure/aks/use-wasi-node-pools
This is a specific solution for AKS correct? I needed more general use. But thanks for the link
Hi @sleipnir I'm fairly sure that Bernard and we have sketched out or are sketching out a lunatics containerd shim implementation.
You CAN use wasi nodepools for this, but let's ping Bernard, because I think there's something there or ongoing. I'll reach out.... and report back here.
@sleipnir On Microsoft docs they say they user Krustlet :) NIce! I really believe in this technology 😄
OK. I had spoken with Bernard a while ago about an implementation via Krustlet, but if they are going in another direction then I wait for the team to define.
Hi @sleipnir, I think for lunatic the best way forward would be a containerd shim (https://github.com/deislabs/runwasi). As Ralph mentioned, I already started experimenting a bit with it, but don't have anything out yet.
Hi @sleipnir, here is a lunatic containerd shim implementation that is based on runwasi. It is actually a collection of containerd shims for Wasm application frameworks and runtimes designed for running Wasm workloads in Kubernetes, including Spin, Wasm Worker Server and Lunatic.
Disclaimer: I work at Azure and I am a core maintainer of containerd/runwasi project.
