-
Notifications
You must be signed in to change notification settings - Fork 382
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
helm: add service monitor scrape interval config #1638
helm: add service monitor scrape interval config #1638
Conversation
f710f8f
to
560bf15
Compare
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
560bf15
to
52f1607
Compare
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.
Thank you for the PR @Jack-R-lantern
I would simplify the Helm values to have:
serviceMonitor:
scrapeInterval: "10s"
It's pretty to common to configure ServiceMonitors like that, and I find the endpoints section in Tetragon Helm values a bit confusing.
@lambdanis Thanks Review, I will change it |
52f1607
to
07a868a
Compare
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.
One docs nit, but looks good otherwise, thank you. The CI failures look unrelated.
07a868a
to
cdb2611
Compare
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.
@Jack-R-lantern It seems a dot in the doc slipped over ;)
I'll take a look at CI, not sure what's wrong there.
The CI failures seem to be a CI bug: #1646 |
this commit was related to the service monitor scrape interval option Signed-off-by: Jack-R-lantern <[email protected]>
cdb2611
to
d23547a
Compare
This commit was related to the service monitor scrape interval option.
I made a change to allow options to be injected via the values.yaml file.
fix: #1633