Istio+Dapr+ consul as nameresolution service invocation encounter a problem

[shuiyunwudi]

Bug Description

###Problem Description I need to user service invocation cross k8s and vm environment，so I config consul as nameresolution; when I integrate dapr with istio, I found the service invocation between application on k8s report error. In my case, there are two application named demo1 and demo2, and demo1 invoke demo2 by " http://localhost:3500/v1.0/invoke/demo2/method/test ". Here are the logs related: the logs of daprd sidecar like that:

the logs of istio-proxy like that:

I have no istio traffic management components deployed (virtual service, destination rule ...) neither in case of dapr api sample application nor in case of demo application. I want to know if anyone else encounter that problem, or know why, I will appreciate your answer.

Version

istio v1.11.4
dapr v1.6.2( or 1.7.2)( mtls disabled)
consul v1.8.3

Additional Information

No response

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2022-05-07. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.