Is opentelemetry-operator installation required? about sumologic-kubernetes-collection

[swiatekm-sumo]

It's required for metrics and tracing instrumentation, you should be fine disabling it if you don't need either of those.

Which operator did you start having problems with, if I may ask? I'd like to report that issue upstream if can be reliably reproduced.

[bkonicek-calm]

Thanks @swiatekm-sumo. The particular operator we had issues with was Airbyte - when a data sync is triggered, the worker service tries to create a Pod in the cluster, but after upgrading to v4 it never started and eventually the sync failed and logged a timeout. I wasn't able to actually find anything in the otel operator logs to confirm this, it's just my best guess.

Some more details on the firewall configuration for webhooks here: open-telemetry/opentelemetry-operator#1009

Our values.yaml is pretty generic. We just have

sumologic:
  clusterName: *******
  accessId: ******
  accessKey: ******
  traces:
    enabled: false
  metrics:
    enabled: false
  setupEnabled: true

[bkonicek-calm]

I can confirm that setting opentelemetry-operator.enabled: false solved this issue