Source of this doc request is https://bugzilla.redhat.com/show_bug.cgi?id=1897490. Severity set to medium.

a) Description of bug report:

[RHOCP4.6] Wrong template is given for configuring Jaeger with Elastic Search in Service Mesh 2.0

b) Bug Description:

The configuration example for configuring Jaeger with Elastic Search in the document [1] is wrong.
It's a configuration for Service Mesh 1.x.
Service Mesh 2.0 we should use "apiversion: maistra.io/v2" according to the document [2].

[1]
https://docs.openshift.com/container-platform/4.6/service_mesh/v2x/ossm-custom-resources.html#ossm-configuring-jaeger-elasticsearch_ossm-custom-resources-v2x
[2]
https://docs.openshift.com/container-platform/4.6/service_mesh/v2x/ossm-custom-resources.html#ossm-cr-example_ossm-custom-resources-v2x
Please provide the correct way to configure Jaeger with ES and fix the document..

Version information:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.1 True False 46h

2. Bug Details:

a) Architectures: 64-bit Intel EM64T/AMD64
x86_64

b) Bugzilla Dependencies:

c) Drivers or hardware dependencies:

d) Upstream acceptance information:

e) External links:

f) Severity (H,M,L):
M

g) How reproducible:
Always

h) Steps to Reproduce:

Step1. The below yaml is mentioned in document [1] to configure Jaeger with Elastic Search which is wrong as per Table 1 in document [2].

apiVersion: maistra.io/v1 ## It uses apiversion "maistra.io/v1" but as per document [2] it should be "maistra.io/v2"
kind: ServiceMeshControlPlane
spec:
istio:
tracing:
enabled: true
ingress:
enabled: true
jaeger:
template: production-elasticsearch
elasticsearch:
nodeCount: 3
redundancyPolicy:
resources:
requests:
cpu: "1"
memory: "16Gi"
limits:
cpu: "1"
memory: "16Gi"

i) Actual results

We are not able to configure Jaeger with Elastic Search as per the given doc in Service Mesh 2.0.

j) Expected results:

Please fix the document so that we can configure Jaeger with Elastic Search in Service Mesh 2.0.

k) Additional Info:

1. oc version
   Client Version: 4.6.1
   Server Version: 4.6.1
   Kubernetes Version: v1.19.0+d59ce34

1. oc get csv -n istio-system
   NAME DISPLAY VERSION REPLACES PHASE
   elasticsearch-operator.4.6.0-202010200139.p0.2 Elasticsearch Operator 4.6.0-202010200139.p0 Succeeded
   jaeger-operator.v1.20.0 Red Hat OpenShift Jaeger 1.20.0 Succeeded
   kiali-operator.v1.24.2 Kiali Operator 1.24.2 kiali-operator.v1.12.16 Succeeded
   servicemeshoperator.v2.0.0 Red Hat OpenShift Service Mesh 2.0.0-0 servicemeshoperator.v1.1.10 Succeeded

3. Business impact:

We cannot configure Jaeger with Elastic Search in Service Mesh 2.0 ,
because the given doc [1] is wrong.

4. Primary contact at Red Hat, email, phone (chat)
mfuruta@redhat.com
5. Primary contact at Partner, email, phone (chat)
fan-wxa@nec.com
(Weiguo Fan)