From istio-support e-mail, we've had two requests in two days for this info (possibly the same customer, but still....)

3/29 Zipkin address with ServiceMesh 2.X
One of my customer  want to use tracing collector tool that is compliant with the zipkin API that is not installed in the cluster but is externally  in Red Hat Service Mesh 2.x 
 
If you refer to the RHSM 1.x documentation (https://docs.openshift.com/container-platform/4.6/service_mesh/v1x/ossm-custom-resources.html#ossm-configuring-jaeger-existing-v1x_ossm-controler-items-v1x)  we can customize the setting to connect using the spec.istio.global.tracer.zipkin.address. But for 2.x i don't see any documents for that. Do we have any documentation or KCS article to achieve the use case.

3/30 Custom Jaeger endpoint in 2.0.  Possible?
We have a case from [customer] asking for configuring a custom (and existing) Jaeger endpoint.
 
It was possible for v1.0 [1] but there's nothing similar for v2.0. Actually in the CRD [2] there's nothing which apparently does the job.
 
Is this even possible? If it is, how? If it's not, is it in the roadmap?
 
References:
[1] https://docs.openshift.com/container-platform/4.6/service_mesh/v2x/ossm-custom-resources.html#configuring-distributed-tracing
[2] https://github.com/maistra/istio-operator/blob/maistra-2.0/manifests-servicemesh/2.0.2/servicemeshcontrolplanes.crd.yaml#L1319
 
The following should work:
 
spec:
  tracing:
    type: None
  techPreview:
    global:
      tracer:
        zipkin:
          address: my-zipkin.address:9411

Note two things here

1 - This is techPreview

2 - It's connecting to an external, non Jaeger service, which is not something we currently support.