-
Bug
-
Resolution: Done
-
Normal
-
None
-
OSSM 3.0-TP1, OSSM 3.0-TP2
-
None
-
3
-
False
-
None
-
False
-
-
In the Red Hat OpenShift Service Mesh 3.0.0tp1 document we have mentioned the wrong extension provider name in the example.
The OTEL resource name is --> otel and in the Istio's spec.values.meshConfig.extensionProviders it is mentioned --> otel-tracing.
Following the example as it is will fail the deployment. We should either use the correct name in the example or mention it explicitly in the document that the extension provider name should matches the OTEL resource name.
kind: OpenTelemetryCollector apiVersion: opentelemetry.io/v1beta1 metadata: name: otel namespace: istio-system spec: ...
apiVersion: sailoperator.io/v1alpha1 kind: Istio metadata: # ... name: default spec: namespace: istio-system # ... values: meshConfig: enableTracing: true extensionProviders: - name: otel-tracing ##<<<<---------It should be otel opentelemetry: port: 4317 service: otel-collector.istio-system.svc.cluster.local
Similarly, in Telemetry resources it should be otel.
apiVersion: telemetry.istio.io/v1 kind: Telemetry metadata: name: otel-demo namespace: istio-system spec: tracing: - providers: - name: otel-tracing ##<<------ randomSamplingPercentage: 100
