You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Kwasm as the medium of easy installation of wasm runtimes and it is such a nice tool. However, I've found that the installer installs all containerd runtimes when in most cases I need just one, at much two. Is it OK if I develop a change for adding args for downloading only certain runtimes despite all? If you don't specify any, then it will have the current behavior.
The text was updated successfully, but these errors were encountered:
Hi @aalonsolopez ,
Great that you're here!
The KWasm installer was build as a one stop solution to experiment with Wasm shims. So, installing all shims is a design decision.
But you are absolutely right, the ecosystem is evolving and in most cases you need exactly one additional runtime. That's why we created the runtime-class-manager under the umbrella of the SpinKube project. It leverages CRDs to install runtimes.
Since the runtime-class-manager project is still in development, you're invited to join us!
Hello, I hope everything is going well :)
I've been using Kwasm as the medium of easy installation of wasm runtimes and it is such a nice tool. However, I've found that the installer installs all containerd runtimes when in most cases I need just one, at much two. Is it OK if I develop a change for adding args for downloading only certain runtimes despite all? If you don't specify any, then it will have the current behavior.
The text was updated successfully, but these errors were encountered: