-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change SM and PM label selector #18
Conversation
Signed-off-by: QuentinBisson <[email protected]>
Tested on gohan |
podMonitorNamespaceSelector: | ||
matchLabels: | ||
name: kube-system | ||
serviceMonitorNamespaceSelector: {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You removed namespace selector! But I wonder about capi management cluster. The Agent will be able to scrape all SMs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All SMs and PMs that have defined application.giantswarm.io/team
.
Meaning it should exclude customer-defined SMs and PMs.
Clever! I like it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes the agent will scrape all SMs so we need to change the condition in PMO https://github.com/giantswarm/prometheus-meta-operator/blob/a536ba2de277fa5a6249581d18feee0b31876b36/service/controller/resource/monitoring/prometheus/resource.go#L351
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hervenicol yes exactly. That way we will pick up managed apps service monitors but not the customer workload :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will also help us enforce that this label is set :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR:
Testing
Tested on a GCP Workload Cluster
Checklist
values.yaml
andvalues.schema.json
are valid.