Could not send spans over gRPC

[andreacoccodi]

Hi all,
I'm running the jaeger-operator helm chart (tried 1.29.0 and 1.32.2) in azure aks with k8s v1.22.6 with istio v1.13.2 and started seeing that error a few months ago after my colleagues raised an issue related to missing spans in elasticsearch.

The jaeger-agents send spans to the jaeger-collector-headless service on port 14250, which in the k8s service is called grpc-http. What seems to be happening is that istio is interpreting that traffic as http instead of http2, which causes the error "Could not send spans over gRPC".

If I manually change the port name to http2-grpc that error goes away, I'm assuming because istio will use the "http2" bit of "http2-grpc" as protocol, as mentioned here https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/.

It's basically what's mentioned here jaegertracing/jaeger-operator#1360, except that all ports but the grpc one are following the protocol-suffix pattern.

Is anyone else seeing this problem?
Thanks