Service Discovery+Mesh healthcheck error

Apologies if this has been answered - I couldn’t locate it. When I use service discovery or the service mesh in isolation, I’m able to get both to work fine. When I try combining them in the form of Spring Cloud Consul Discovery and enabling the service mesh using connect-inject = true for all pods, the health checks fail on the consul UI.

For context I have an k8s/eks setup on aws using multiple pods for a single service. When connect-inject is not enabled, the consul server is able to reach the pods directly using the podIP’s. However, if connect-inject is enabled, using the podIP no longer works. How should the server be reaching the individual pods in order to ascertain the health check?

the consul server is able to reach the pods directly using the podIP’s

Why is the Consul server calling out to the service pods?

I think if you open up a bug with the Helm yaml and your service yaml and step-by-step reproduction that might be best.