pat-s and justusbunsi
9f0b65f386
Fix unittests ( #434 )
...
Unclear why it only appeared now and not earlier.
Co-authored-by: justusbunsi <[email protected] https://gitea.com/gitea/helm-chart/pulls/434
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected]
2023-04-14 14:45:37 +08:00
pat-s
a9779c9724
Bump to 1.19.1 ( #433 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/433
Co-authored-by: pat-s <[email protected] [email protected]
2023-04-14 02:25:37 +08:00
pat-s
c0b2fdf8fa
Remove discord webhook ( #435 )
...
Broken since a long time and probably not used by anyone
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/435
Reviewed-by: techknowlogick <[email protected] [email protected] [email protected]
2023-04-14 02:21:21 +08:00
pat-s
00395e79b0
Add resource specs to init container ( #423 )
...
Supersedes stalled #362
I opted for defining `requests` while leaving `limits` open. This might help for scheduling without restricting performance during init.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/423
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected]
2023-04-01 19:35:11 +08:00
pat-s
25500d7ca2
Ignore Chart.lock for formatters/linters ( #424 )
...
This might hopefully help with the formatting issues around `Chart.lock`.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/424
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected]
2023-04-01 19:18:17 +08:00
pat-s
87c59b2fca
Format all files with prettier VSCode plugin and add yamllint in CI ( #413 )
...
@justusbunsi to end my formatting mess... ;)
I am not fully sure myself about the linebreaks in `values.yaml` but I don't think there's an easy way to change that behavior.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/413
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected]
2023-03-29 05:18:23 +08:00
pat-s and justusbunsi
6915a4b401
Add chart author ( #411 )
...
and format YAML
(maybe we should also update the maintainers list if some are not active anymore?)
Co-authored-by: justusbunsi <[email protected] https://gitea.com/gitea/helm-chart/pulls/411
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected]
2023-03-29 05:12:10 +08:00
pat-s
a0ba3c9bef
Bump memcached to add arm64 support ( #422 )
...
And allow overriding the `image` section so users could possible also use other image tags.
fix #285
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/422
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected]
2023-03-29 05:11:33 +08:00
pat-s
ae9a71ea11
Remove mysql and mariadb chart deps ( #417 )
...
As discussed in Discord.
Supersedes #412 and #407 .
**⚠️ BREAKING**
Users depending on the built-in MySQL or MariaDB chart have to switch to an self-managed database, or Postgres
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/417
Reviewed-by: justusbunsi <[email protected] [email protected] [email protected] [email protected] [email protected]
2023-03-29 01:02:04 +08:00
pat-s and justusbunsi
5cb0802b7b
[Breaking] Bump postgres chart to latest release ( #391 )
...
See discussion in #387
Upgrade notes to Chart v11.x and Postgres 14.x: https://docs.bitnami.com/kubernetes/infrastructure/postgresql/administration/upgrade/
The current version in Gitea is using `11.11.0-debian-10-r62` from 2021-04.
Bumping the chart to the latest (v12.x) would use the image `15.2.0-debian-11-r14` which would be a jump from postgres 11 to postgres 15. There are no specific notes for the v12.x chart release, hence we might be able to just go to 12.x directly.
There have been some param renamings which I've reflected in the README.
**⚠️ BREAKING**
Users have to migrate their Postgres DB by e.g. restoring a previously created database dump into a clean installation.
Co-authored-by: justusbunsi <[email protected] https://gitea.com/gitea/helm-chart/pulls/391
Reviewed-by: techknowlogick <[email protected] [email protected] [email protected] [email protected]
2023-03-28 01:12:29 +08:00
pat-sandjustusbunsi
