5876a9e7fc
Update Gitea to 1.19.2 and bump chart deps ( #442 )
...
No substantial changes in chart deps.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/442
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-30 11:05:33 +08:00
c274911aab
README: one sentence per line ( #440 )
...
Fix #376
Editors should do the job of soft-wrapping in case a line get's too long.
One sentence per line simplifies reviews and diffs a lot as it let's one comment on a piece of text that is contextually sound and not split over multiple lines.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/440
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-19 23:01:03 +08:00
0861260c5d
update to use actions for testing PRs ( #439 )
...
Run PR tests using Gitea Actions
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/439
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Co-committed-by: techknowlogick <techknowlogick@gitea.io >
2023-04-15 04:21:00 +08:00
d8bb352765
Fix aws secrets ( #438 )
...
@lunny
It still looks like that the IAM user does not have enough permissions for the S3 sync operation.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/438
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-14 21:06:43 +08:00
76e47ef6f0
Add -y to fix apt install on ci
2023-04-14 18:19:41 +08:00
95076eb11f
Fix yaml lint
2023-04-14 16:08:04 +08:00
e768a6acdc
Fix release tag ci
2023-04-14 15:49:18 +08:00
7434556b37
Use Gitea Actions for release publishing ( #436 )
...
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/436
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Co-committed-by: techknowlogick <techknowlogick@gitea.io >
2023-04-14 14:54:34 +08:00
9f0b65f386
Fix unittests ( #434 )
...
Unclear why it only appeared now and not earlier.
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/434
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-14 14:45:37 +08:00
a9779c9724
Bump to 1.19.1 ( #433 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/433
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-14 02:25:37 +08:00
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 <techknowlogick@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-14 02:21:21 +08:00
bfaf822a36
feat: Add support for setting priorityClassName ( #430 )
...
### Description of the change
Adds support for setting priorityClassName on the Gitea pod.
### Benefits
Users can take advantage of https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/ with Gitea.
### Applicable issues
- fixes #429
### Checklist
<!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
- [x] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/430
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: Casey Buto <cbuto@d2iq.com >
Co-committed-by: Casey Buto <cbuto@d2iq.com >
2023-04-07 18:58:34 +08:00
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 <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-01 19:35:11 +08:00
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 <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-04-01 19:18:17 +08:00
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 <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-03-29 05:18:23 +08:00
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 <justusbunsi@noreply.gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/411
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-03-29 05:12:10 +08:00
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 <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-03-29 05:11:33 +08:00
0f4e1e488a
remove mariadb and mysql from _helpers.tpl ( #421 )
...
### Description of the change
Removes checks for mariadb and mysql from _helpers.tpl
### Benefits
Fixes the helm-chart version 8.0.0 if using a external database
### Applicable issues
- fixes #420
- fixes #419
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/421
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Reviewed-by: delvh <dev.lh@web.de >
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io >
Co-authored-by: Maximilian Marschall <maximilian.marschall@3xm.at >
Co-committed-by: Maximilian Marschall <maximilian.marschall@3xm.at >
2023-03-29 03:02:29 +08:00
fb5c615f61
Bump Gitea to 1.19.0 ( #418 )
...
As title.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/418
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io >
2023-03-29 01:10:15 +08:00
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 <justusbunsi@noreply.gitea.io >
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-03-29 01:02:04 +08:00
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 <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/391
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-03-28 01:12:29 +08:00
fdac9e9048
Support for SSH log level ( #358 )
...
Re https://gitea.com/gitea/helm-chart/issues/224#issuecomment-717087
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/358
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: strk <strk@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: pi3ch <pi3ch@noreply.gitea.io >
Co-committed-by: pi3ch <pi3ch@noreply.gitea.io >
2023-03-22 16:13:31 +08:00
1be9fae08b
test: use official unittest plugin ( #410 )
...
### Description of the change
Switch to official `helm-unittest` which is now alive again at https://github.com/helm-unittest/helm-unittest
### Applicable issues
- ref #199
### Checklist
<!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
- [ ] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
- [ ] Breaking changes are documented in the `README.md`
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/410
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: Michael Kriese <michael.kriese@visualon.de >
Co-committed-by: Michael Kriese <michael.kriese@visualon.de >
2023-03-21 23:53:13 +08:00
4869aed6ad
Fix wrong reference to existingKey
( #415 )
...
### Description of the change
Fix a wrong reference to `signing.existingKey`, `signing.existingSecret` was what was meant and what is used in the chart.
### Benefits
Less confusion when trying to use the Helm chart.
### Possible drawbacks
Evangelists of `existingKey` storming the barricades even though `existingKey` is long dead.
### Applicable issues
None, nobody noticed enough to care, apparently.
Co-authored-by: Tobias Wolter <towo@towo.eu >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/415
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: towo <towo@noreply.gitea.io >
Co-committed-by: towo <towo@noreply.gitea.io >
2023-03-21 14:16:41 +08:00
9a6cb4d357
Make test pods optional and allow image override ( #360 )
...
### Description of the change
Make the test-connection Pod optional and override the wget container's image.
### Benefits
Allows users to enable/disabled the test-connection Pod and override the wget container's image.
### Checklist
- [X] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
- [X] Breaking changes are documented in the `README.md`
Co-authored-by: Umer Anwar <umer.anwar@nuance.com >
Co-authored-by: ooms97 <anwarumer97@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/360
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: ooms97 <ooms97@noreply.gitea.io >
Co-committed-by: ooms97 <ooms97@noreply.gitea.io >
2023-03-09 23:25:45 +08:00
452aeadddf
Add section describing versioning and update policy ( #347 )
...
After recent discussions in Discord.
Feel free to modify as needed!
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/347
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.io >
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Co-committed-by: pat-s <pat-s@noreply.gitea.io >
2023-03-09 01:14:33 +08:00
c46bf7c60f
Format README ( #408 )
...
Some small formatting changes which are auto-applied by the markdown code styler in vscode (which I am using a lot).
These are also present in #407 .
Merging this before/in general would help be a bit when tinkering with the README.
Mainly indentation related, plus some single quotes -> double quotes changes.
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/408
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.io >
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Co-committed-by: pat-s <pat-s@noreply.gitea.io >
2023-03-08 03:50:40 +08:00
18100cca11
Fixup Chart.lock inconsistency ( #406 )
...
Introduced with b6d275c4f5
Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/406
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2023-02-26 22:42:43 +08:00
b6d275c4f5
Update memcached and use new OCI registry ( #405 )
...
OCI registry: https://blog.bitnami.com/2023/01/bitnami-helm-charts-available-as-oci.html
fixes #404
I think we should switch all other binami charts to also use the new OCI registry as according to their blog post, this will be the future method they're heading to.
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/405
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-02-26 20:52:32 +08:00
578a6cb867
Bump Gitea to 1.18.5 ( #403 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/403
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
2023-02-22 04:38:08 +08:00
01bb9b4a77
Add support for hostAliases ( #401 )
...
### Description of the change
It is required to add custom mapping between hostnames and IP addresses for the gitea pods to be able to access external services like oauth providers or webhook servers.
It is common to take global variables for the entires and set them using hostAliases in the pod template.
### Benefits
Give us more flexibility when using gitea in various network environments.
### Applicable issues
- fixes #400
### Checklist
- [X] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
Co-authored-by: Taekyun Kim <tkq.kim@samsung.com >
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/401
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: podain77 <podain77@noreply.gitea.io >
Co-committed-by: podain77 <podain77@noreply.gitea.io >
2023-02-22 01:53:25 +08:00
513ad81228
Bump Gitea to 1.18.4 ( #402 )
...
Signed-off-by: siretart <siretart@tauware.de >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/402
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Co-authored-by: siretart <siretart@noreply.gitea.io >
Co-committed-by: siretart <siretart@noreply.gitea.io >
2023-02-21 05:09:04 +08:00
e47edbddf9
use drone secrets for s3 info ( #399 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/399
2023-02-08 05:57:32 +08:00
da4120809f
Bump Gitea to 1.18.3 ( #397 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/397
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
2023-01-24 00:53:20 +08:00
83c184826b
bump to 1.18.2
2023-01-20 14:26:45 +08:00
ccec32c144
Bump Gitea image to 1.18.1 ( #395 )
...
As title: Bump Gitea image to 1.18.1.
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/395
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2023-01-18 19:40:04 +08:00
19e9b07e6e
Re-add GPG configuration feature ( #374 )
...
This reverts d5ce1a47ea
and therefore adds the GPG feature back into main.
As it is a breaking change, this PR now also contains the required upgrade notes.
Closes #107 again.
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/374
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: John Olheiser <john+gitea@jolheiser.com >
2023-01-18 00:58:10 +08:00
8b6a00603a
Update 'values.yaml' ( #394 )
...
### Description of the change
Corrects the spelling of the word deprecated.
### Benefits
Documentation free of misspelled words is more likely to be viewed as "professional".
### Possible drawbacks
None that I can think of
### Applicable issues
- fixes #393
### Additional information
There may be other misspelled words or incorrectly phrased passages that aren't addressed in this PR.
For reference, see the online dictionary for the correct spelling of deprecated.
https://www.merriam-webster.com/dictionary/deprecated
### Checklist
- [X] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
- [X] Breaking changes are documented in the `README.md`
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/394
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: robv89r <robv8r@noreply.gitea.io >
Co-committed-by: robv89r <robv8r@noreply.gitea.io >
2023-01-10 14:54:55 +08:00
6574b1b232
Ignore unrelated helm files from bundling ( #385 )
...
<!--
Before you open the request please review the following guidelines and tips to help it be more easily integrated:
- Describe the scope of your change - i.e. what the change does.
- Describe any known limitations with your change.
- Please run any tests or examples that can exercise your modified code.
Thank you for contributing! We will try to review, test and integrate the change as soon as we can.
-->
### Description of the change
Exluding non helm chart related files from release artifact
### Benefits
Smaller release artifacts
### Possible drawbacks
Exluded files not visible any within the artifact
### Applicable issues
None
### Additional information
None
### ⚠ BREAKING
None
### Checklist
<!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
- [x] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
- [x] Breaking changes are documented in the `README.md`
Co-authored-by: Julian Schlarb <js@project-deadline.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/385
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: JSchlarb <jschlarb@noreply.gitea.io >
Co-committed-by: JSchlarb <jschlarb@noreply.gitea.io >
2022-12-28 18:30:15 +08:00
4f7bc17d34
Bump alpine version in CI ( #384 )
...
To fix package installation issues. Apparently installing `helm` in 3.16 fails constantly.
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/384
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Co-committed-by: pat-s <pat-s@noreply.gitea.io >
2022-12-27 17:18:36 +08:00
279bacb941
v1.17.4
2022-12-22 08:18:31 +08:00
9ed671d685
Switch to official npm release of readme generator ( #375 )
...
This is a follow up for #369 . They published the package on NPM.
https://github.com/bitnami-labs/readme-generator-for-helm/issues/36
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/375
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-12-05 20:56:08 +08:00
d5ce1a47ea
Temporary revert GPG feature for semver based retagging ( #373 )
...
Feature #343 happens to be a breaking change when enabling `.Values.signing` but not specifying
any of the new private key properties. Tag `v6.0.2` is therefore not following semantic versioning.
This temporarily reverts commit b8f0310c43
and a fix-up commit 57a1cd27d9
to retag 6.0.2 as 6.0.3.
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/373
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
2022-10-21 00:35:19 +08:00
57a1cd27d9
Gpg init fails to import key ( #371 )
...
### Description of the change
The init container for gpg key import doesn´t work. There is a not a tty error.
### Benefits
This will run gpg in batch mode. Eliminating the tty error.
### Possible drawbacks
None that I can think off.
### Applicable issues
- fixes #370
### Checklist
- [X] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
- [X] Breaking changes are documented in the `README.md`
Co-authored-by: Jeroen Verhoeven <jeroen@joentje.org >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/371
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: dajoen74 <dajoen74@noreply.gitea.io >
Co-committed-by: dajoen74 <dajoen74@noreply.gitea.io >
2022-10-18 13:47:21 +08:00
6c59fe361d
v1.17.3
2022-10-17 04:19:45 +08:00
d1f5dca573
Lock readme-generator-for-helm dependency ( #369 )
...
With every push on main/master branch of that repository, the referenced
tarball is replaced, causing npm integrity checks to fail. Locking the used
reference to a specific commit hash is more reliable.
There is an open issue regarding publishing on NPM. As long as this is
not resolved, we would need to use this workaround to get updates.
(https://github.com/bitnami-labs/readme-generator-for-helm/issues/36 )
Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/369
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-10-14 00:16:41 +08:00
b8f0310c43
Add gpg configuration settings ( #343 )
...
### Description of the change
This PR adds support for gpg key setup. It allows to pass the gpg private key content inline inside `values.yaml` or refer to an existing secret containing the key content data.
### Benefits
Administrators don't need to manually setup the gpg environment from inside a running container. It also eliminates the breaking change of Gitea 1.17 regarding `[git].HOME` as the `GNUPGHOME` environment variable is used consistently to relocate the `.gnupg` directory to its former location.
### Applicable issues
- fixes #107
### Additional information
This PR add the first unit tests to this Helm Chart, ensuring templating integrity for signing related configuration.
### Checklist
- [x] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm )
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/343
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-09-28 16:18:59 +08:00
0d1f748898
check existence of /data/gitea/conf/
instead of /data/gitea/
( #310 )
...
### Description of the change
Checking the existence of the config directory should be done with the directory path itself. Not its parent directory.
This simple fix addresses that by using the config directory for its existence check.
### Benefits
Prior to #337 there was no other way to install this helm chart using the `extraVolumeMounts` setting with these values:
```yaml
replicaCount: %d
extraVolumes:
- name: config-volume
configMap:
name: %s
extraVolumeMounts:
- name: config-volume
mountPath: /data/gitea/templates/custom
```
Without this fix, the Gitea pod would never initialize, and would crashloop with the same error in #296 .
### Additional information
Mounting a configMap to `/data/gitea/templates/custom` causes the `/data/gitea` folder to exist even though the `/data/gitea/conf` had not been initialized yet. The initialization script saw that the `/data/gitea` dir existed and exited early without initializing `/data/gitea/conf`.
Co-authored-by: cboin1996 <christianboin@hotmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/310
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: cboin1996 <cboin1996@noreply.gitea.io >
Co-committed-by: cboin1996 <cboin1996@noreply.gitea.io >
2022-09-26 04:08:56 +08:00
6e5ae5c912
Increase line length linter to 200 ( #355 )
...
As discussed in #348
fix #348
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/355
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Co-committed-by: pat-s <pat-s@noreply.gitea.io >
2022-09-25 23:21:52 +08:00
bb26a872e9
1.17.2
2022-09-07 09:21:38 +08:00
51bb72090e
bogus commit
2022-08-23 03:22:30 +08:00
58d21e07f9
Bump Gitea version to 1.17.1 ( #353 )
...
### Description of the change
Bumps Gitea version to 1.17.1. 🙂
### Applicable issues
- fixes #340
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/353
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: Andrew Thornton <art27@cantab.net >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-08-23 02:51:21 +08:00
299d6db142
Split "extraVolumeMounts" into init and container mounts ( #337 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/337
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: lafriks <lafriks@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-08-08 03:32:19 +08:00
a4ab5f981f
Skip processing non-provided additional configs ( #336 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/336
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-08-04 21:46:04 +08:00
7801c9c5c9
Pre-generate LFS_JWT_SECRET during init phase ( #335 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/335
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: lafriks <lafriks@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-08-04 20:47:24 +08:00
58fc28f6d0
fix: correctly handle tls ingress ( #94 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/94
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: huww98 <huww98@outlook.com >
Co-committed-by: huww98 <huww98@outlook.com >
2022-07-28 16:29:33 +08:00
32735ed4df
Restructure changelog/upgrading approach ( #331 )
...
Description of the change
Mostly, this change just moves the changelog to the bottom of the README which helps new users to see the actual documentation. As the structure for the changes itself is slightly different, there are some changes in wording so that it still makes sense. But mostly structural changes.
The change within the dependency section is due to a broken link since auto-generating the parameters section. Now there are links to every dependency related parameters.
Benefits
It helps us to maintain a clear structure for the README of this project.
Possible drawbacks
Our users are currently trained to look at the top of the document to see the changes. They now have to scroll down or use the quick link from installation section.
Applicable issues
fixes #247
Additional information
Every version section starts with a disclaimer right now. This is duplicated and might hide important text due to its existence. A centralized intruduction at top of the upgrading section tells the reader what to expect from that whole section.
I've also noticed that on ArtifactHub the emotes are not rendered correctly. So I replaced them with the actual ones and reduced their usage. That way it better highlights those parts the reader must not miss.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/331
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-07-16 01:27:48 +08:00
aa97cdab5b
Restore default behavior description for image tag ( #330 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/330
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: wxiaoguang <wxiaoguang@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-07-10 04:43:04 +08:00
bc16cc8134
add dnsConfig value support ( #329 )
...
Description of the change
Add support for a new value: dnsConfig, to be passed to the statefulset pod template configuration.
Default is {}, and does not change anything from current default pod configuration.
Benefits
Ability to fix some issues encountered with Alpine-based docker images, which may break DNS resolving on some clusters.
In particular, this allows to lower the ndots value, which fixes DNS resolving of FQDNs.
dnsConfig:
options:
- name: ndots
value: "1"
Also, with this setting, one can set other parameters to finely tune DNS configuration for Gitea pods, if needed:
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config
Possible drawbacks
None.
Additional information
Some relevant links about the issue this setting allows to fix:
https://stackoverflow.com/questions/65181012/does-alpine-have-known-dns-issue-within-kubernetes
https://gitlab.alpinelinux.org/alpine/aports/-/issues/9017
Checklist
Parameters are documented in the values.yaml and added to the README.md using readme-generator-for-helm
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/329
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: dek <dek@noreply.gitea.io >
Co-committed-by: dek <dek@noreply.gitea.io >
2022-06-27 14:35:55 +08:00
33586d26cf
Describe breaking changes for 6.0.0 ( #327 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/327
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: wxiaoguang <wxiaoguang@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-06-23 23:41:10 +08:00
0172a59889
Properly lock chart dependencies ( #326 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/326
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-06-15 15:37:25 +08:00
2cc3195eaa
Improve contribution part of this repository ( #328 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/328
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-06-13 03:35:24 +08:00
b3b91e2044
generate readme Parameters from values.yaml ( #323 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/323
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: cnfatal <cnfatal@noreply.gitea.io >
Co-committed-by: cnfatal <cnfatal@noreply.gitea.io >
2022-06-09 19:21:25 +08:00
9cb822f41c
add global values support ( #322 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/322
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: cnfatal <cnfatal@noreply.gitea.io >
Co-committed-by: cnfatal <cnfatal@noreply.gitea.io >
2022-06-09 18:55:08 +08:00
e59fbc4008
feat: switch to github raw url for bitnami charts ( #324 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/324
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: takirala <takirala@noreply.gitea.io >
Co-committed-by: takirala <takirala@noreply.gitea.io >
2022-06-03 13:50:12 +08:00
a466206d9e
1.16.8
2022-05-17 09:01:34 +08:00
80032dfc5c
1.16.7
2022-05-02 13:36:55 +08:00
52ed32ae74
Allow configuration of ipFamilyPolicy and ipFamilies ( #313 )
...
To enable access to e.g. the SSH port by IPv6, the selection of ipFamilyPolicy and ipFamilies service attributes is necessary. Enable the possibility to configure these by helm values.
Co-authored-by: Sven Fischer <sven@leiderfischer.de >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/313
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: svenihoney <svenihoney@noreply.gitea.io >
Co-committed-by: svenihoney <svenihoney@noreply.gitea.io >
2022-04-25 19:56:25 +08:00
b06b3edf1d
Consider imagePullPolicy for init containers ( #317 )
...
The default behaviour for container image pulls depend on different values
such as image tag usage and its value.
See https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting
It leads to an unintended behaviour for this Helm Chart. Kubernetes
will always pull the image for init containers when using the `latest`
Gitea image tag, even if `Values.image.pullPolicy` defines a different
value for the runtime container.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/317
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: Gusted <williamzijl7@hotmail.com >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-04-22 06:13:19 +08:00
a7bc46015e
feat: configurable annotations for gitea StatefulSet ( #315 )
...
Fixes #314
Right now, the gitea StatefulSet does not allow any annotations to be configured via the helmchart - see https://gitea.com/gitea/helm-chart/src/tag/v5.0.4/templates/gitea/statefulset.yaml#L4-L6
My use case:
I am trying to use Reloader (https://github.com/stakater/Reloader ) so that I can configure my values.yaml such that i can set some annotations on the StatefulSet and thus Reloader can rollout a restart of gitea StatefulSet whenever a watched secret or configmap is updated.
Co-authored-by: Tarun Gupta Akirala <tarugupta.92@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/315
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: takirala <takirala@noreply.gitea.io >
Co-committed-by: takirala <takirala@noreply.gitea.io >
2022-04-21 23:55:53 +08:00
46b190adda
1.16.6
2022-04-21 09:03:01 +08:00
d94226765d
close #302
...
Signed-off-by: techknowlogick <techknowlogick@gitea.io >
2022-03-26 02:28:39 +08:00
844c8daa0b
1.16.5
...
Signed-off-by: techknowlogick <techknowlogick@gitea.io >
2022-03-24 10:59:17 +08:00
982ae60d8e
1.16.4
...
Signed-off-by: techknowlogick <techknowlogick@gitea.io >
2022-03-15 06:16:48 +08:00
62b82459de
Consider environment variables during app.ini creation ( #298 )
...
This PR improves the handling and injection into _app.ini_ of user defined environment variables via env-to-ini script.
Fixes #297
Co-authored-by: Lucas Hahn <lucas.hahn@novum-rgi.de >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/298
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: 6543 <6543@obermui.de >
2022-03-09 14:47:55 +08:00
9530967163
1.16.3 ( #300 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/300
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
2022-03-04 16:32:18 +08:00
d35de55248
Remove db connection check ( #299 )
...
This will remove the db connection check, which has caused some trouble in the past.
It will now simply run _gitea migrate_ and output a message, if the database is not available.
Co-authored-by: Lucas Hahn <lucas.hahn@novum-rgi.de >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/299
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: luhahn <luhahn@noreply.gitea.io >
Co-committed-by: luhahn <luhahn@noreply.gitea.io >
2022-03-02 08:25:49 +08:00
78b5858009
Simplify version handling ( #250 )
...
- Drop super legacy `image.version` value (see #92 description)
- Always use `appVersion` from Chart.yaml as image tag if non specified
---
Don't know whether this is a breaking change regarding image.version
drop.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/250
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-03-01 22:55:44 +08:00
1a3ce54dfc
update to 1.16.2 ( #293 )
...
replaces #290
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/293
2022-02-26 06:01:16 +08:00
6896c7caae
added hostPort support for ssh ( #276 )
...
This fixes my feature request (#275 ) to support hostPort to expose the ssh port.
Co-authored-by: alex <alex@zengers.de >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/276
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: a-zen <a-zen@noreply.gitea.io >
Co-committed-by: a-zen <a-zen@noreply.gitea.io >
2022-02-25 17:18:57 +08:00
7bdf742e81
Add example for Kubernetes secret as additional source ( #294 )
...
As discussed in #286 , an example for using Kubernetes secrets as additional configuration source was missing. This adds it.
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/294
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-02-14 16:00:47 +08:00
f2948646ba
Fix markdown lint in CI ( #295 )
...
I saw a few PRs including this. Maybe it's good to have this as fast as possible to prevent others providing this fix, too.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/295
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2022-02-10 23:44:41 +08:00
c010c3857e
update to gitea 1.15.10 ( #278 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/278
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Co-committed-by: techknowlogick <techknowlogick@gitea.io >
2022-01-20 16:22:36 +08:00