Applyig mTLS breaks the communication between jaeger collector and cassandra

3

Istio version: 1.5.2

Details below:

Helm Charts: https://github.com/jaegertracing/helm-charts/tree/master/charts/jaeger

Configuration steps used:

  1. Open the values.yaml and configure cassandra as follows:
    provisionDataStore:
    cassandra: true
    elasticsearch: false

  2. create a kubernetes namespace “jaeger” and enable istio auto injection

  3. Deploy mTLS policies. Create a directory called policies under templates and place the mTLS and destination route policies.

  4. Deploy the hem charts.
    helm install -n jaeger --namespace jaeger .

  5. Observe the pods

[kubectl get pods -n jaeger

NAME READY STATUS RESTARTS AGE
jaeger-agent-jn8kv 2/2 Running 0 7m38s
jaeger-agent-k7v5k 2/2 Running 0 7m38s
jaeger-cassandra-0 2/2 Running 0 7m38s
jaeger-cassandra-1 1/2 CrashLoopBackOff 3 5m55s
jaeger-collector-6965df75-lmfxl 1/2 CrashLoopBackOff 6 7m38s
jaeger-query-5bbcb9cb84-d589c 2/3 CrashLoopBackOff 6 7m38s

  1. check the pod logs of jaeger-collector and istio-proxy under it.

Please let me know if you need further details.