Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.
Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space like `krustlet` which rely on `wasmtime` under the hood.
Ref:
* Wasmedge integration: https://github.com/containers/crun/pull/774
* Wasmer integration: https://github.com/containers/crun/pull/742
* https://github.com/krustlet/krustlet
Signed-off-by: Aditya R <arajan@redhat.com>
Crun supports running `wasm` workload on kubernetes natively. Both the
standard CRI implementation `cri-o` and `containerd` supports that.
Following commit adds documentation for both of them.
Signed-off-by: Aditya Rajan <arajan@redhat.com>
