vikarna

#######edgemesh-gw######### I0509 23:27:24.846112 1 http.go:137] destination svc is default.ws-svc I0509 23:27:24.846250 1 log.go:184] DEBUG: add [2] handlers for chain [tcp] I0509 23:27:24.846343 1 handler.go:58] l4 proxy get tcpserver address: worker:10.85.0.96:8080...

I tried both with and without port. / # ./client --addr 192.168.64.18 connecting to ws://192.168.64.18/echo read: websocket: close 1006 (abnormal closure): unexpected EOF / # ./client --addr 192.168.64.18:80 connecting to...

No, It's the node IP on which edgemesh gw is running. I have given the gw config above.

multiple virtual services are not working. For example gateway: *.abc.com vs1: app.abc.com vs2: test.abc.com vs3: new.abc.com Is this expected behavior?

apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: edgemesh-gateway spec: selector: kubeedge: edgemesh-gateway servers: - hosts: - '*' port: name: http-0 number: 23333 protocol: HTTP

ok. Is there any plan to develop this feature?