tetratelabs/proxy-wasm-go-sdk

wasm-plugin does not work except 'istio-proxy' namepsace

ydkmm opened this issue · 2 comments

Describe the bug / error

the wasm-plugin does not work except 'istio-proxy' namepsace.
the wasmplugin aim to add a header in http header. when i kubectl this wasm-plugin into istio-proxy namespace, the header was added and the request was matched by virtualserivce into subset v2. but once deployed into other namespace for example mm-tmp, the header was added but can not be matched by virtual service

What is your Envoy/Istio version?

client version: 1.16.3
control plane version: 1.16.3
data plane version: 1.16.3 (38 proxies)

What is the SDK version?

What is your TinyGo version?

tinygo version 0.30.0 windows/amd64 (using go version go1.20.7 and LLVM version 16.0.1)

URL or snippet of your code including Envoy configuration

Additional context (Optional)

i use centos to curl the servcie
centos
curl
destinationrule
httpbinv1
httpbinv2
virtualservice
wasm-plugin

image
when the wasm-plugin was deployed into mm-tmp namesapce, the header was added,but the request cannot be matched by virtualserice into subset v2

the question is nothing to do with SDK. maybe ask in the Istio slack?