Ideally the WASM Pod is reachable as service from other cluster pods. In practice, krustlet doesn't support networking yet and the WASI standard itself isn't supporting it yet https://github.com/deislabs/krustlet/issues/505. The feasible path is to instead reach the running pod using k8s exec API. The latter is also easier said then done, issues are explained in https://github.com/deislabs/krustlet/issues/513
Epic #56
Ideally the WASM Pod is reachable as service from other cluster pods. In practice, krustlet doesn't support networking yet and the WASI standard itself isn't supporting it yet https://github.com/deislabs/krustlet/issues/505. The feasible path is to instead reach the running pod using k8s
execAPI. The latter is also easier said then done, issues are explained in https://github.com/deislabs/krustlet/issues/513There isn't any official documentation on how kubectl exec works exactly or how the endpoint should behave. Some reverse engineering is available at https://erkanerol.github.io/post/how-kubectl-exec-works/ or can be deduced from how kube clients work https://github.com/clux/kube-rs/blob/33207f9589/kube/src/api/subresource.rs#L500