Don't make cloudflare receiver require TLS

[xbglowx]

Component(s)

receiver/cloudflare

Is your feature request related to a problem? Please describe.

Trying to expose a cloudflare logpush endpoint using the cloudflare receiver and noticed that it is a requirement to configure TLS. This is not need in all setups, especially when the service is being hosted behind a LB or proxy that handles TLS

Describe the solution you'd like

Make TLS optional

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/cloudflare: @dehaansa @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[djaglowski]

@xbglowx, would you be willing to make a PR for this?

[xbglowx]

@xbglowx, would you be willing to make a PR for this?

I could try, but I am really rusty at golang. Any tips before I attempt to start on this?

[dehaansa]

The cloudflare LogPush integration itself had a strict TLS requirement when this was implemented.

Do you have some evidence that LogPush no longer strictly required TLS?

[xbglowx]

The cloudflare LogPush integration itself had a strict TLS requirement when this was implemented.

Do you have some evidence that LogPush no longer strictly required TLS?

It still requires TLS, but if this receiver is sitting behind a proxy that handles TLS, do you also need this? For example, I am trying to run this on k8s and we already have TLS configured with cert-manager and Solo's Gloo VirtualService.

[dehaansa]

It still requires TLS, but if this receiver is sitting behind a proxy that handles TLS, do you also need this? For example, I am trying to run this on k8s and we already have TLS configured with cert-manager and Solo's Gloo VirtualService.

I misunderstood your original question, I think that could most likely work.

[xbglowx]

Is there a slack channel that we can use, so that I can ask you some questions?

[xbglowx]

For the time being, I came up with #26629

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/cloudflare: @dehaansa @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[xbglowx]

Should be able to close this as fixed.

[djaglowski]

Closed by #26629