3 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
volker.raschekandpat-s	edd8557bb0	docs(README): hint of CPU limit lower than 1000m (#795) ... The example of my latest PR based on a cpu resource limit of `100m`. But as the article describes, a cpu limit of lower than `1000m` or `1` can also lead to cpu throttling. I've updates the README, to be correct and inform the user to take care of a correct cpu resource limit. Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/795 Reviewed-by: pat-s <pat-s@noreply.gitea.com> Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems> Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>	2025-02-19 09:24:31 +00:00
volker.raschekandjustusbunsi	4f42f4bee3	[Close #771] fix: set GOMAXPROCS (#772) ... The following patch add automatically the environment variable `GOMAXPROCS`, when a CPU limit is defined. Otherwise CPU throttling may occur. Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/772 Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com> Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.com> Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems> Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>	2025-02-02 21:30:00 +00:00
volker.raschekandpat-s	e636984db1	feat(serviceMonitor): custom configuration (#710) ... 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. Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/710 Reviewed-by: pat-s <pat-s@noreply.gitea.com> Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems> Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>	2024-09-18 17:55:28 +00:00