Collector Contrib fails to recognise "insecure" option

[iNikem]

Describe the bug
When provided with the following simple configuration, collector-contrib fails to start:

receivers:
  otlp:
    protocols:
      grpc:

exporters:
  otlp:
    endpoint: backend:8080
    insecure: true

service:
  pipelines:
    traces:
      receivers: [ otlp ]
      exporters: [ otlp ]

Error:

Error: cannot load configuration: error reading exporters configuration for otlp: 1 error(s) decoding:

* '' has invalid keys: insecure

What version did you use?
Docker image otel/opentelemetry-collector-contrib:latest, version 0.34.0

Docker image otel/opentelemetry-collector:latest, version 0.34.0 works find without any error.

[iNikem]

I have just noticed, why latest docker image uses 0.34, when latest version is 0.36? But still, this does not explain the difference between core and contrib collectors

[mx-psi]

open-telemetry/opentelemetry-collector#4063 changed the way this setting is specified (it is now under the tls section), so probably it explains this

[bogdandrutu]

@iNikem see previous comment, that was a breaking change unfortunately.

[iNikem]

Does this mean that https://opentelemetry.io/docs/collector/configuration/#exporters and https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/otlpexporter/README.md and related docs were left unchanged?

[iNikem]

Also, why the difference between core and contrib images?

[almeidaalex]

open-telemetry/opentelemetry-collector#4063 changed the way this setting is specified (it is now under the tls section), so probably it explains this

I've changed my config to:

 jaeger:
    endpoint: jaeger-all-in-one:14250
    tls:
      insecure: true

Now it's not complaining about this error

[ganga-sah]

open-telemetry/opentelemetry-collector#4063 changed the way this setting is specified (it is now under the tls section), so probably it explains this

I've changed my config to:

 jaeger:
    endpoint: jaeger-all-in-one:14250
    tls:
      insecure: true

Now it's not complaining about this error

thanks @almeidaalex for the tip! You unblocked me!

[dmitryax]

Closing the issues since all the documentation looks updated to the new configuration interface

[delanym]

Just got burnt by this again because I forget that
https://hub.docker.com/r/otel/opentelemetry-collector/tags?page=1&name=latest
isn't updated anymore

[mx-psi]

Just got burnt by this again because I forget that https://hub.docker.com/r/otel/opentelemetry-collector/tags?page=1&name=latest isn't updated anymore

This is tracked at open-telemetry/opentelemetry-collector-releases/issues/73, please upvote the issue there if fixing this would have helped you