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'm not sure what the output of the build here is but it appears it creates a custom Envoy build that you have to replace your standard sidecar with. I noticed Istio and Envoy are trying to push WebAssembly plugins hosted on WebAssemblyHub so you can reference plugins from there and not have to use custom Envoy builds.
Is that something which could be considered here? I'd love to make use of the functionality but I'm not allowed to use a custom Istio sidecar in our environment.
The text was updated successfully, but these errors were encountered:
@tillig I think ultimately, it makes sense to move this functionality into a WebAssembly Module. But although the community is working very hard to get this functionality ready for prime time, I think it's not there yet. This particular project is deployed via an additional sidecar + + . Have a look at the examples in this repo.
If you want to bootsrap the idea @tillig you can maybe create a branch and try to compile this using proxy-wasm in an example? Most of the times when porting something to WASM is the libraries and dependencies that should be compatible or that should be able to run over WASI.
I'm not sure what the output of the build here is but it appears it creates a custom Envoy build that you have to replace your standard sidecar with. I noticed Istio and Envoy are trying to push WebAssembly plugins hosted on WebAssemblyHub so you can reference plugins from there and not have to use custom Envoy builds.
Is that something which could be considered here? I'd love to make use of the functionality but I'm not allowed to use a custom Istio sidecar in our environment.
The text was updated successfully, but these errors were encountered: