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
Adding extra labels to the selector in serviceMonitor does not change the output. Specifically, this line in the falco chart config seems to have no impact.
I unsuccessfully tried defining selector labels both with matchLabels: and without.
Is this intended behavior? (I'm no expert.)
Why does it matter?
Our ArgoCd changes the instance label of the Falco Service after deployment. Then, the selector labels used by the ServiceMonitor do not match anymore and the Service is not discovered.
I would like to overwrite the app.kubernetes.io/instance: falco selector to solve this issue.
Thank you for your hard work!
How to reproduce it
Use the falco helm chart.
Change the following settings:
metrics:
enabled: trueserviceMonitor:
create: trueselector:
app.kubernetes.io/instance: my-falcofoo: bar
Observe generated ServiceMonitor config to see that the defined selectors are missing:
# in ServiceMonitor/falco.yaml# ...selector:
matchLabels:
app.kubernetes.io/instance: falcoapp.kubernetes.io/name: falcotype: falco-metrics
Expected behaviour
The labels defined in the selector section should appear in the final config like this:
# in ServiceMonitor/falco.yaml# ...selector:
matchLabels:
app.kubernetes.io/instance: my-falcoapp.kubernetes.io/name: falcotype: falco-metricsfoo: bar
Adding extra labels to the selector in serviceMonitor does not change the output. Specifically, this line in the falco chart config seems to have no impact.
I unsuccessfully tried defining selector labels both with
matchLabels:
and without.Is this intended behavior? (I'm no expert.)
Why does it matter?
app.kubernetes.io/instance: falco
selector to solve this issue.Thank you for your hard work!
How to reproduce it
falco
helm chart.Expected behaviour
The labels defined in the selector section should appear in the final config like this:
Environment
Additional context
From what I can tell this is because the file
charts/falco/templates/serviceMonitor.yaml
only has the following section:In comparison, adding labels to the ServiceMonitor works. The template code for that section looks as follows:
If the described behavior is not intended, then this might be a good place to start.
The text was updated successfully, but these errors were encountered: