Tyler Helmuth

See https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-operator/UPGRADING.md#0540-to-0552. Trying with the latest chart version should solve your problem

Although typically appVersion corresponds directly with the thing being installed, I think since the operator version and target allocator version and auto-instrumentation versions are so closely related I'd be ok...

The OpenTelemetryCollector CRD allows you to specify the collector image it uses. The collector image in the chart sets the Operator's default collector image, but the CRD allows overriding. The...

Like all collector distributions you'll only have access to configure the components included in the distribution. If you configure a component that is not included the collector will not start....

The reason I don't want to do it in one breaking change is that the breaking change won't happen on install but after the collector tried to start up. For...

I'm good with that. And I think it should be its own PR, not the 0.98.0 bump.

@DevProJSSV have you tried following https://opentelemetry.io/docs/kubernetes/getting-started or https://opentelemetry.io/docs/demo/kubernetes-deployment/?

@TheJarX are you also experiencing an error? The original issue is definitely happening bc the image being used does not contain the components it should. This was likely caused by...

@roychshao you can try with a latest OCB and collector components, but I have been unable to reproduce your issue. The error message indicates that the first component in each...

I am no familiar with `Airflow`, is it the source of metrics and is it sending over OTLP? If you done want the `otel default metrics` remove the prometheus receiver.