Component(s)

collector

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

Currently, the Operator creates several K8s services corresponding to a collector custom resource. In scenarios where the collector is deployed as a daemonset and does not play the role of a server and is used purely as a scraping client (say prometheus scraping as an example), the K8s services are not required.

Creating the K8s service by default, especially the ClusterIp one, adds a lot of overhead by wasting rev space in etcd, creating NAT tables for kube-proxy etc. This is particularly impactful on large clusters where a churn in the daemonset pods can lead more impact.

Describe the solution you'd like

An option to disable the creation of K8s services, similar to https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/values.yaml#L516.

Describe alternatives you've considered

No response

Additional context

No response