Skip to content

Internal Telemetry config doesn't support insecure_skip_verify #13835

@martinjt

Description

@martinjt

Component(s)

No response

What happened?

Describe the bug
Unless I'm missing something in the code, I can't see a way to specific the insecure_skip_verify flag which is needed if people are using Self-signed certificates.

This seems to be because it isn't available in the opentelemetry-configuration project. So I've created open-telemetry/opentelemetry-configuration#292 to see if it can be added.

Steps to reproduce

Use a backend that's secured using a Self-signed certificate that you can't trust in the container.

What did you expect to see?
The exporter can be configured to send to it

What did you see instead?
Certificate errors

Collector version

0.133.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

service:
  telemetry:
    traces:
      processors:
        - batch:
            exporter:
              otlp:
                protocol: grpc
                endpoint: ${env:ASPIRE_ENDPOINT}
                headers:
                  - name: "x-otlp-api-key"
                    value: ${env:ASPIRE_API_KEY}
                # insecure_skip_verify: true # NOT SUPPORTED

Log output

Additional context

No response

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcollector-telemetryhealthchecker and other telemetry collection issues

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions