-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
Version of components:
OpenShift version: 4.17.0-0.nightly-2024-07-20-191204
opentelemetry-operator.v0.104.0
Description of the problem:
When a OpenTelemetry Collector instance with enableMetrics is created in a non openshift- prefixed namespace, the namespace of the instance doesn't show in the OpenTelemetry Collector dashboard Namespace drop-drown.
Steps to reproduce the issue:
1. Deploy and install the OpenTelemetry operator built off the latest upstream branch.
2. Create a OTEL collector instance with enableMetrics:true in the collector config in a non openshift prefixed namespace.
% oc project chainsaw-otlp-metrics Already on project "chainsaw-otlp-metrics" on server "https://api.ikanse-221.qe.devcluster.openshift.com:6443". % oc get pods NAME READY STATUS RESTARTS AGE cluster-collector-collector-955ff8465-9fwpc 1/1 Running 0 101m jaeger-allinone-6d485545f-2j2fk 1/1 Running 0 3h52m telemetrygen-metrics-ll5pq 0/1 Completed 0 101m telemetrygen-traces-69xkv 0/1 Completed 0 101m
3. Check the namespace drop-down in the OpenTelemetry collector dashboard. The OTEL collector instance namespace is not shown. However the instance can be seen and selected in the collector instance drop-down.