5c39511d9a
fix(deployment): adapt nodeSelector test
2025-12-18 20:11:38 +01:00
1b22954570
fix(deployment): avoid duplicated nodeSelector #980
2025-11-05 19:11:28 +01:00
72606192a6
refactor(structure): remove leading gitea directory ( #958 )
...
The following pull request removes the `gitea` directory. With regard to maintaining act_runners in a separate git repository or helm chart, this additional directory becomes redundant.
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/958
Reviewed-by: DaanSelen <daanselen@noreply.gitea.com >
Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems >
Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems >
2025-10-02 11:36:47 +00:00
10ad0f7743
style: adapt indentation of extraInitContainer tests
2025-08-19 12:49:01 +02:00
kostovicmb
4cfcbd729f
feat(deployment): support further initContainers
...
The following patch intoduce the dictionaries pre and postExtraInitContainers.
The dictionaries can be used to specify further initContainers before and after
the gitea initializing process. For example:
```yaml
postExtraInitContainers:
- name: foo
image: docker.io/library/busybox:latest
preExtraInitContainers:
- name: bar
image: docker.io/library/busybox:latest
```
2025-08-19 12:24:33 +02:00
pat-s
a94eec4238
refactor: migrate ingress definition out of beta ( #679 )
...
### Description of the change
Redesigned ingress configuration to align better with implicit best practices.
### Benefits
- Smarter defaults
- More tests
- Remove [deprecated API Versions](extensions/v1beta1) (e.g. `extensions/v1beta1`) and always use `networking.k8s.io/v1`
### Possible drawbacks
Hopefully 🙃 none
### Applicable issues
fix #674
### Additional information
- Define `ingress.annotations` via helpers
- Move tests from `tests/deployment` to `tests/ingress`
- Use own tests file for ingress tpl tests
- Ensure defaults of `path` and `pathType` are always rendered
- Set top-level default value for `ingress. pathType`
- Change default of `ingress.hosts[0].paths` to `[]` to ensure proper rendering via template
### âš BREAKING
I think all of these changes should be backward comp with existing ingress definitions, but surely worth highlighting in the changelog of the release.
### 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`
- [x] Templating unittests are added
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.com >
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/679
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2025-05-16 13:08:27 +00:00
developerguy
a7035ca4e5
feat: make it configurable of the initContainers volume mount path for scripts ( #848 )
...
### Description of the change
Makes it configurable volume mount path for initContainers for init scripts
### Benefits
Configurable initContainers volumeMount path for init scripts
### Possible drawbacks
I don't think that there will be any drawbacks
### Applicable issues
- Fixes #847
Signed-off-by: Batuhan Apaydin <batuhan.apaydin@chainguard.dev >
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/848
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.com >
Co-authored-by: developerguy <developerguy@noreply.gitea.com >
Co-committed-by: developerguy <developerguy@noreply.gitea.com >
2025-04-03 18:03:13 +00:00
Ceddaerrix
1f313ac70e
feat: adding dry support to gitea additional config from envs parameter ( #840 )
...
### Description of the change
Based on the discussion under https://gitea.com/gitea/helm-gitea/issues/60 , it is possible to use `gitea.additionalConfigFromEnvs` to provide variables in order to override configurations from `app.ini`.
Especially when using gitea as a dependency of an umbrella, some values may need to be repeated in multiple places (such has database configuration). Hence, introducing the `tpl` function on `gitea.additionalConfigFromEnvs` will simplify such repetition by having the value only set in one place...
### Benefits
With the same intentions as https://gitea.com/gitea/helm-gitea/pulls/759 , https://gitea.com/gitea/helm-gitea/pulls/664 , https://gitea.com/gitea/helm-gitea/pulls/529 or https://gitea.com/gitea/helm-gitea/pulls/498 , this change will allow reusing the value from other value parameters to avoid duplicating the same value in multiple places.
### Possible drawbacks
N/A
### Applicable issues
N/A
### Additional information
N/A
### Checklist
- [X] Helm templating unittests are added (required when changing anything in `templates` folder)
Co-authored-by: 212597596 <cedric.henry@ge.com >
Co-authored-by: pat-s <pat-s@noreply.gitea.com >
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/840
Reviewed-by: pat-s <pat-s@noreply.gitea.com >
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.com >
Co-authored-by: Ceddaerrix <ceddaerrix@noreply.gitea.com >
Co-committed-by: Ceddaerrix <ceddaerrix@noreply.gitea.com >
2025-03-30 14:30:35 +00:00
bachorp
2c78da9c3e
docs: set full path of values.yaml key in output to user ( #832 )
...
generate-chart / generate-chart-publish (push) Has been cancelled
Currently, the reported path of the values to be changed is not always correct (especially `gitea.persistence` vs. `persistence`).
Co-authored-by: techknowlogick <techknowlogick@noreply.gitea.com >
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/832
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com >
Co-authored-by: bachorp <bachorp@noreply.gitea.com >
Co-committed-by: bachorp <bachorp@noreply.gitea.com >
2025-03-26 17:16:17 +00:00
pat-s
7245b3b4cc
chore: change repo name to helm-gitea ( #823 )
...
Co-authored-by: techknowlogick <techknowlogick@gitea.com >
Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/823
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com >
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 >
2025-03-06 20:54:40 +00:00
techknowlogick
ff7783fcbe
chore: use docker.gitea.com registry URLs ( #814 )
...
Due to ratelimits
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/814
Reviewed-by: pat-s <pat-s@noreply.gitea.com >
Co-authored-by: techknowlogick <techknowlogick@gitea.com >
Co-committed-by: techknowlogick <techknowlogick@gitea.com >
2025-02-28 10:48:04 +00:00
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
justusbunsi
a79fd31f7e
Increase testability of shell scripts ( #752 )
...
This is a preparation for #724 (bash script testing) which would be too complex to review if done there.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/752
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Co-committed-by: justusbunsi <sk.bunsenbrenner@gmail.com >
2024-12-19 12:04:00 +00:00
justusbunsi
4691b63f7a
Move Helm unittests into subfolder ( #750 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/750
Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com >
Co-committed-by: justusbunsi <sk.bunsenbrenner@gmail.com >
2024-12-18 12:04:15 +00:00
