v1.24.3 ztunnel throwing intermittent warnings/errors under load when ingress-nginx in ambient mode

[rchincha]

ingress-nginx (in ambient mode) forwarding to a simple http (sidecar or ambient) with mtls=strict
stressed with a jmeter load tester.

What does the following (happening intermittently) mean and have folks seen this before? asking since jmeter is throwing errors intermittently.

2025-05-12T23:34:14.427312Z warn access connection failed src.addr=10.224.0.5:60629 dst.addr=10.244.2.149:15006 direction="inbound" error="attempted
recursive call to ourselves"
2025-05-12T23:34:36.350936Z warn access connection failed src.addr=10.224.0.4:49395 dst.addr=10.244.2.149:15006 direction="inbound" error="attempted
recursive call to ourselves"
2025-05-12T23:34:38.207933Z warn access connection failed src.addr=10.224.0.5:38635 dst.addr=10.244.2.149:15006 direction="inbound" error="attempted
recursive call to ourselves"
2025-05-12T23:34:44.874931Z warn access connection failed src.addr=10.224.0.4:46507 dst.addr=10.244.2.149:15006 direction="inbound" error="attempted
recursive call to ourselves"
2025-05-12T23:34:46.508531Z warn access connection failed src.addr=10.224.0.6:50819 dst.addr=10.244.2.149:15006 direction="inbound" error="attempted

[rchincha]

Don't see this when ingress-nginx is in sidecar mode.

[rchincha]

There are others.

2025-05-12T23:46:53.368891Z error access connection complete src.addr=10.224.0.5:56512 dst.addr=10.244.0.243:80
dst.service="ingress-nginx-controller.ingress-nginx.svc.cluster.local" dst.workload="ingress-nginx-controller-b779c8c5f-q8rzb"
dst.namespace="ingress-nginx" direction="inbound" bytes_sent=0 bytes_recv=0 duration="10000ms" error="connection failed: deadline has elapsed"

[howardjohn]

is your application legitimately sending to port 15006 or is that a Istio issue?