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
Is your feature request related to a problem? Please describe.
Currently, when the collector is creating podMonitors is using a predefined set of labels configured here. Since the pods we want to configure have different labels (as they are running a service the collector is only a sidecar of), the labels are not matched and the pods are not monitored.
Describe the solution you'd like
I'd like to inject a set of custom labels to any pod injected with the opentelemetry collector sidecar, and then match these labels in the podMonitor.
Describe alternatives you've considered
Creating the podMonitor manually.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Could it be a solution to add those labels + the ones you define for your OTEL Collector? Those labels could be propagated to the created PodMonitor and achieve what you want.
That could work but in order for the podMonitor to match arbitrary workloads injected with the sidecar there has to be a flag that allows omission of these labels (since labels like app.kubernetes.io/instance which are currently used are very common, and will probably be defined differently for each workload.
If that makes sense I can take a stab at implementing this myself.
Component(s)
collector
Is your feature request related to a problem? Please describe.
Currently, when the collector is creating podMonitors is using a predefined set of labels configured here. Since the pods we want to configure have different labels (as they are running a service the collector is only a sidecar of), the labels are not matched and the pods are not monitored.
Describe the solution you'd like
I'd like to inject a set of custom labels to any pod injected with the opentelemetry collector sidecar, and then match these labels in the podMonitor.
Describe alternatives you've considered
Creating the podMonitor manually.
Additional context
No response
The text was updated successfully, but these errors were encountered: