Anthos service mesh

[ravichandra]

I installed Anthos service mesh on a GKE cluster. I enabled external access for few microservices in my GKE cluster using nginx's ingress-nginx-controller.  I enabled automatic sidecar proxy so that I can monitor services in ASM dashboard. When I'm sending requests to my application I'm getting this issue: upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111

Will the sidecar proxy container in application pods will just monitor the traffic and send the telemtry data to ASM dashboard or will it hold the requests? I don't see any logs related to this error too

[Marvin_Lucero]

Hi @ravichandra ,

Are you using Network Policies with Dataplanv2? Assuming that this is your setup, please check this documentation regarding Network Policy drops a connection due to incorrect connection tracking lookup.

To mitigate this issue you would need to configure the port and containerPort in the Service manifest to be the same value.

[ravichandra]

No, I'm not using dataplanv2.
 gke version:
Client Version: v1.26.3
Kustomize Version: v4.5.7
Server Version: v1.24.9-gke.3200

istioctl version
client version: 1.13.3
control plane version: 1.16.4
data plane version: none

I configured port and containerPort in the service manifest to be the same value.