Tracing Sprint #42
Description of the issue:
An update of the Jaeger Operator in spring enabled TLS communication by default between a Jaeger sidecar agent and the Jaeger collector. Since then, when the Jaeger sidecar is injected in a Pod that also has an Istio sidecar running, the Jaeger agent logs show such error:
Err :connection error: desc = \"transport: authentication handshake failed: tls: first record does not look like a TLS handshake\". Reconnecting...","system":"grpc","grpc_log":true}
The failed TLS handshake is also reported in the collector's log.
Removing the annotation to inject the Istio sidecar leads to the Pod being redeployed and Jaeger successfully sending information to the collector.
Jaeger and Istio were installed as part of Service Mesh and run in the same istio-system namespace.
- $ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.3.19 True False 20h Cluster version is 4.3.19
- $ oc get csv -n istio-system
NAME DISPLAY VERSION REPLACES PHASE
elasticsearch-operator.4.3.27-202006211650.p0 Elasticsearch Operator 4.3.27-202006211650.p0 Succeeded
jaeger-operator.v1.17.3 Red Hat OpenShift Jaeger 1.17.3 Succeeded
kiali-operator.v1.12.13 Kiali Operator 1.12.13 kiali-operator.v1.12.12 Succeeded
servicemeshoperator.v1.1.4 Red Hat OpenShift Service Mesh 1.1.4 servicemeshoperator.v1.1.3 Succeeded