feat(serviceMonitor): custom configuration #710
Reference in New Issue
Block a user
No description provided.
Delete Branch "refs/pull/710/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This patch extends the serviceMonitor resource to specify a custom TLS
configuration used by prometheus to scrape the metrics.
Furthermore, the interval and scrapeTimeout can now be adapted without changing
the global defaults of the prometheus instance.
Thanks!
Did you run
make readme
? This should actually reduce the changes toREADME.md
to a minimum.If we add this, we should note that dependency in the README somewhere.
I've adapted the documentation of
gitea.metrics.serviceMonitor.enabled
. If this is not enough, I will be happy to write a few more lines in the README.Ah sorry, just realized that
serviceMonitor
is nested belowmetrics
and hence this dependency should be clear. But I see you already changed it, thanks!@ -463,4 +358,3 @@
## @param gitea.metrics.enabled Enable Gitea metrics
## @param gitea.metrics.token used for `bearer` token authentication on metrics endpoint. If not specified or empty metrics endpoint is public.
## @param gitea.metrics.serviceMonitor.enabled Enable Gitea metrics service monitor. Requires, that `gitea.metrics.enabled` is also set to true, to enable metrics generally.
## @param gitea.metrics.serviceMonitor.interval Interval at which metrics should be scraped. If not specified Prometheus' global scrape interval is used.
-> Missing dot after "scraped".
I have fixed this in the latest commits.
Missing dot again.
I have fixed this in the latest commits, too.
@ -470,7 +364,6 @@ gitea:
## @param gitea.metrics.serviceMonitor.tlsConfig TLS configuration to use when scraping the metric endpoint by Prometheus.
prometheus -> Prometheus
Fixed
LGTM
Given that we just issued a release, this will be queued for the next one which has to wait a bit.
You should be able to use the branch until then, if urgent.
Let's see if @justusbunsi has some comments until then :)
Hi @pat-s,
have you heard anything from @justusbunsi ?
@volker.raschek
Apologies for the silence. Was on vacation. Have to catch up several things and cannot review in detail. From a quick review, nothing to add.
Thanks for the PR.
Hi @pat-s and @justusbunsi,
can you release a new version of this chart with the latest available gitea version?
I can than switch back to the normal release cycle instead of using a dedicated branch, which includes my patch.
Scheduled for today.
🚀 Released with https://gitea.com/gitea/helm-chart/releases/tag/v10.5.0