Commit Graph
18 Commits
Author SHA1 Message Date
volker.raschek 9bf4e11faa fix(values): add missing persistence configuration of valkey primary and replica
changelog / changelog (push) Successful in 8s
check-and-test / check-and-test (push) Successful in 33s
2026-01-23 23:25:50 +01:00
volker.raschek cf45403920 docs(README): add postgresql-ha.persistence.storageClass
changelog / changelog (push) Successful in 7s
check-and-test / check-and-test (push) Successful in 1m30s
2026-01-23 22:53:35 +01:00
volker.raschek e87d534a23 fix(values): add options to disable persistence of dependencies
changelog / changelog (push) Successful in 7s
check-and-test / check-and-test (push) Failing after 1m26s
The following patch inherits the default values of the dependencies like
postgresql-ha, postgresql, valkey-cluster and valkey to disable persistent
storage.

For users, this is more obvious than having to look up the configuration options
in the dependencies or subcharts themselves.
2026-01-23 22:50:38 +01:00
volker.raschek aa3cf45660 fix(Makefile): add yamllint as dedicated target
changelog / changelog (push) Successful in 12s
check-and-test / check-and-test (push) Successful in 34s
2025-11-05 19:03:11 +01:00
volker.raschek 064e51d0c2 style(yamllint): add missing new line 2025-11-05 19:00:49 +01:00
volker.raschek b88abaa1e7 fix(deployment): avoid duplicated nodeSelector #980
changelog / changelog (push) Has been cancelled
check-and-test / check-and-test (push) Has been cancelled
2025-11-05 18:31:45 +01:00
volker.raschek 1d49cf3f58 fix(Chart): add annotation 'artifacthub.io/links'
changelog / changelog (push) Successful in 14s
check-and-test / check-and-test (push) Successful in 35s
2025-10-12 12:13:40 +02:00
volker.raschekandtechknowlogick 89017545d3 fix(deps): use bitnamilegacy images (#962)
changelog / changelog (push) Successful in 8s
check-and-test / check-and-test (push) Successful in 1m32s
The following PR overwrites the `registry`, `repository` and `tag` attributes of the dependencies to download the images from the `bitnamilegacy` repository.

This allows us to redeploy the v12 release stream, even though we are no longer receiving updates for the bitnami images.

Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/962
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com>
Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems>
Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>
2025-10-05 18:11:37 +00:00
volker.raschekandLunny Xiao d9e181df93 chore: update maintainers list - volker.raschek (#933)
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/933
Reviewed-by: delvh <dev.lh@web.de>
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems>
Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>
2025-08-20 16:32:23 +00:00
volker.raschek 10ad0f7743 style: adapt indentation of extraInitContainer tests 2025-08-19 12:49:01 +02:00
volker.raschek e31bd265b1 docs(README): fulfill MD044/proper-names 2025-08-19 12:44:12 +02:00
volker.raschekandMarkus Pesch 468c12643f fix(renovate): add lockFileMaintenance (#924)
The following patch adapts the renovate configuration maintain lockfiles, for
example the package-lock.json

Further information can be found in the official documentation:

https://docs.renovatebot.com/configuration-options/#lockfilemaintenance

Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/924
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems>
Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>
2025-08-13 07:24:29 +00:00
volker.raschekandtechknowlogick 82190f3d30 docs(README): be compliant with markdownlint (#923)
changelog / changelog (push) Successful in 8s
check-and-test / check-and-test (push) Successful in 1m46s
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/923
Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems>
Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>
2025-08-12 15:04:57 +00:00
volker.raschekandpat-s 09767c4494 docs(README): add workaround for rotating TLS certificates (#907)
The following patch extends the README of an additional chapter, how to handle
rotating TLS certificates mounted as secret into the container filesystem.

Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/907
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-07-19 13:08:03 +00:00
volker.raschekandpat-s ec7a659535 feat: add Artifacthub annotation 'artifacthub.io/changes' (#881)
The following PR add the annotation 'artifacthub.io/changes'. For each semantic
commit will be the annotation extended. Further information can be found in the
documentation of
[Artifacthub.io](https://artifacthub.io/docs/topics/annotations/helm/#supported-annotations).

The CI has been adapted. The binary jq as well as yq in >= v4.0 is required.
Otherwise will not be concatenated the YAML file correctly via the yq expression,
because the `loadstr()` expression is not available in lower versions.

Additionally the relation between the semantic commit and the Artifacthub.io
change log type should be clarified. The current relationshiop can be adapted if
needed.

Furthermore, yq will be installed as part of the CI steps. It would be great if
yq is also available as deb package in >=v4.0. This would reduce the boiler
plate to install yq and maintain the version via renovate.

Regarding the renovate expression. In my environment works this expression, but
I don't know if it also works in this gitea/renovate instance.

Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/881
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-06-16 14:20:39 +00:00
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