You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)// +optionalModeMode`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.// +optionalIngressstruct {
// Type default value is: none// Supported types are: route/loadbalancer/nodeport/nginx-ingress-v1/ingressTypestring// Hostname by which the ingress proxy can be reached.Hostnamestring...
}
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?
The text was updated successfully, but these errors were encountered:
frzifus
changed the title
[Enhancement] Option to expose exporters outside of cluster
[Enhancement] Option to expose collector outside of cluster
Jul 25, 2022
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
:What are your thoughts on this?
Insecure bool
that comes with a defaultfalse
value.)ServiceType
in the existing or create an additonal one like<APP>-collector-external
?Might be related:
The text was updated successfully, but these errors were encountered: