open-telemetry / opentelemetry-operator

Kubernetes Operator for OpenTelemetry Collector
Apache License 2.0
1.19k stars 430 forks source link

Unable to add oauth2client extension to Sidecar pod created by Operator #769

Closed umarkhan17 closed 2 years ago

umarkhan17 commented 2 years ago

I am unable to add oauth2client extension to sidecar agent collector pod.

My side-car.yaml

apiVersion: opentelemetry.io/v1alpha1 kind: OpenTelemetryCollector metadata: name: sidecar-for-ms namespace: central-observability spec: mode: sidecar image: harbor-test.crisil.com/observability/opentelemetry-collector config: | extensions: oauth2client: client_id: agent client_secret: secret token_url: http://some-loadbalancer.url:8080/auth/realms/opentelemetry/protocol/openid-connect/token receivers: jaeger: protocols: grpc: otlp: protocols: grpc: http: zipkin: endpoint: 0.0.0.0:9411

exporters: logging: zipkin: endpoint: http://some-loadbalancer-2.url/zipkin/api/v2/spans auth: authenticator: oauth2client

service: extensions: [oauth2client] pipelines: traces/agent: receivers: [jaeger,otlp,zipkin] processors: [] exporters: [logging,zipkin]

in my sidecar pod, i am getting logs like :

Error: failed to get config: cannot unmarshal the configuration: unknown extensions type "oauth2client" for "oauth2client" (valid values: [pprof zpages memory_ballast health_check]) 2022/03/14 06:43:33 collector server run finished with error: failed to get config: cannot unmarshal the configuration: unknown extensions type "oauth2client" for "oauth2client" (valid values: [pprof zpages memory_ballast health_check])

umarkhan17 commented 2 years ago

Turns out i was using opentelemetry-collector image for my sidecar in PodSpec.Image. to use oauth2client we need to use opentelemetry-collector-contrib image.