Add optional ingress for otel collector

[pragmaticivan]

It might be useful for exposing the collector for SPA apps (react) and perhaps adding another way of redirecting requests to a oauth proxy.

[dmitryax]

Hi @secustor @pragmaticivan , can you please provide more evidence why the ingress should be part of the collector helm chart?

The general idea is to keep this helm chart thin and provide only necessary resources to support OpenTelemetry collector in k8s environment.

I don't believe that ingress has to be part of this chart. I think it should be deployed with nginx-ingress helm chart separately.

[secustor]

I'm not sure, if we talk about the same.

What I'm referencing is a simple Ingress object like in my PR, which cannot be deployed using the nginx-ingress helm chart. Usually these are packaged with the corresponding applications. e.g. Loki from Grafana and Jaeger

Regarding the addition of an ingress controller to this helm chart. I'm of your opinion, this should not be included in this helm chart.

My use case is to ingest data from external applications which are instrumentalized with Opentelemetry.
To secure the endpoint an API gateway is used and most API gateway implementations, I'm aware of, utilize ingress objects as basis for their configurations.

[pragmaticivan]

Same as above. This ticket was intended for the Ingress resource, not the operator.