[Enhancement] Option to expose collector outside of cluster

[frzifus]

I may ask first - what is the best way to expose a collector to reach it from an edge device or another cluster?

---

Original post that was moved.

After creating an collector as `deployment`, `daemonset` or `statefulset` this results in three services using the default type `ClusterIP`. Looking at the implementation ([service.go](https://github.com/open-telemetry/opentelemetry-operator/blob/2a66583d739ca3b355cbbcc02052dbc08b8c3c88/pkg/collector/reconcile/service.go#L122)), it seems that there is no way to change this type. We could now manually create or patch a service with e.g. the `ServiceType=LB`. But from my point of view, it would be quite nice to be able to specify this immediately in the CRD.

As an extension of the CRD, I was thinking of something like this ingress entry in the following code snipped. (Inspired by the Skupper operator[1])

File opentelemetrycollector_types.go:

	// Mode represents how the collector should be deployed (deployment, daemonset, statefulset or sidecar)
	// +optional
	Mode Mode `json:"mode,omitempty"`

	// Ingress is used to specify how OpenTelemetry Collector is exposed. This
	// function is only available if one of the valid modes is set.
	// Valid modes are: deployment, daemonset and statefulset.
	// +optional
	Ingress struct {
		// Type default value is: none
		// Supported types are: route/loadbalancer/nodeport/nginx-ingress-v1/ingress
		Type string

		// Hostname by which the ingress proxy can be reached.
		Hostname string
            
                ...
	}

What are your thoughts on this?

• Does it make sense to you?
• Suggestions for additional entries? (maybe something to prevent exposing the collector without any protection? Like a Insecure bool that comes with a default false value.)
• Would it make more sense to set the ServiceType in the existing or create an additonal one like <APP>-collector-external?

---

Might be related:

• [Enhancement] Possibility to add services for custom exporters #931
• Is there an option to create hostport service using operator  #252
• Document operator use cases involving service configuration #839
• Create serving certs for headless services on OpenShift (#818) #824

[pavolloffay]

This seems to be a duplicate of #902

[frzifus]

oh i didnt see it 👍