35fcb41ce2
1.20.3
generate-chart / generate-chart-publish (push) Has been cancelled
2023-08-21 16:07:51 +00:00
5e148748ce
Update documentations link to new addresses and some other links update ( #482 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/482
Reviewed-by: pat-s <pat-s@noreply.gitea.com >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-committed-by: Lunny Xiao <xiaolunwen@gmail.com >
2023-08-03 07:25:52 +00:00
1ea6cb4633
1.20.2
generate-chart / generate-chart-publish (push) Has been cancelled
2023-07-31 09:04:23 +02:00
269ca48586
1.20.1
2023-07-22 10:50:27 +02:00
aa8f543c08
bump to 1.20 nightly for env-to-ini fix
generate-chart / generate-chart-publish (push) Has been cancelled
2023-07-19 23:08:55 +02:00
ede76d4b68
update helm deps and add makefile rule
generate-chart / generate-chart-publish (push) Has been cancelled
2023-07-17 21:26:45 +02:00
8e27bb9bae
[Breaking] Add HA-support; switch to Deployment
( #437 )
...
# Changes
A big shoutout to @luhahn for all his work in #205 which served as the base for this PR.
## Documentation
- [x] After thinking for some time about it, I still prefer the distinct option (as started in #350 ), i.e. having a standalone "HA" doc under `docs/ha-setup.md` to not have a very long README (which is already quite long).
Most of the information below should go into it with more details and explanations behind all of the individual components.
## Chart deps
~~- Adds `meilisearch` as a chart dependency for a HA-ready issue indexer. Only works with >= Gitea 1.20~~
~~- Adds `redis` as a chart dependency for a HA-ready session and queue store.~~
- Adds `redis-cluster` as a chart dependency for a HA-ready session and queue store (alternative to `redis`). Only works with >= Gitea 1.19.2.
- Removes `memcached` instead of `redis-cluster`
- Add `postgresql-ha` as default DB dep in favor of `postgres`
## Adds smart HA chart logic
The goal is to set smart config values that result in a HA-ready Gitea deployment if `replicaCount` > 1.
- If `replicaCount` > 1,
- `gitea.config.session.PROVIDER` is automatically set to `redis-cluster`
- `gitea.config.indexer.REPO_INDEXER_ENABLED` is automatically set to `false` unless the value is `elasticsearch` or `meilisearch`
- `redis-cluster` is used for `[queue]` and `[cache]` and `[session]`mode or not
Configuration of external instances of `meilisearch` and `minio` are documented in a new markdown doc.
## Deployment vs Statefulset
Given all the discussions about this lately (#428 ), I think we could use both.
In the end, we do not have the requirement for a sequential pod scale up/scale down as it would happen in statefulsets.
On the other side, we do not have actual stateless pods as we are attaching a RWX to the deployment.
Yet I think because we do not have a leader-election requirement, spawning the pods as a deployment makes "Rolling Updates" easier and also signals users that there is no "leader election" logic and each pod can just be "destroyed" at anytime without causing interruption.
Hence I think we should be able to switch from a statefulset to a deployment, even in the single-replica case.
This change also brought up a templating/linting issue: the definition of `.Values.gitea.config.server.SSH_LISTEN_PORT` in `ssh-svc.yaml` just "luckily" worked so far due to naming-related lint processing. Due to the change from "statefulset" to "deployment", the processing queue changed and caused a failure complaining about `config.server.SSH_LISTEN_PORT` not being defined yet.
The only way I could see to fix this was to "properly" define the value in `values.yaml` instead of conditionally definining it in `helpers.tpl`. Maybe there's a better way?
## Chart PVC Creation
I've adapted the automated PVC creation from another chart to be able to provide the `storageClassName` as I couldn't get dynamic provisioning for EFS going with the current implementation.
In addition the naming and approach within the Gitea chart for PV creation is a bit unusual and aligning it might be beneficial.
A semi-unrelated change which will result in a breaking change for existing users but this PR includes a lot of breaking changes already, so including another one might not make it much worse...
- New `persistence.mount`: whether to mount an existing PVC (via `persistence.existingClaim`
- New `persistence.create`: whether to create a new PVC
## Testing
As this PR does a lot of things, we need proper testing.
The helm chart can be installed from the Git branch via `helm-git` as follows:
```
helm repo add gitea-charts git+https://gitea.com/gitea/helm-chart@/?ref=deployment
helm install gitea --version 0.0.0
```
It is **highly recommended** to test the chart in a dedicated namespace.
I've tested this myself with both `redis` and `redis-cluster` and it seemed to work fine.
I just did some basic operations though and we should do more niche testing before merging.
Examplary `values.yml` for testing (only needs a valid RWX storage class):
<details>
<summary>values.yaml</summary>
```yml
image:
tag: "dev"
PullPolicy: "Always"
rootless: true
replicaCount: 2
persistence:
enabled: true
accessModes:
- ReadWriteMany
storageClass: FIXME
redis-cluster:
enabled: false
global:
redis:
password: gitea
gitea:
config:
indexer:
ISSUE_INDEXER_ENABLED: true
REPO_INDEXER_ENABLED: false
```
</details>
## Preferred setup
The preferred HA setup with respect to performance and stability might currently be as follows:
- Repos: RWX (e.g. EFS or Azurefiles NFS)
- Issue indexer: Meilisearch (HA)
- Session and cache: Redis Cluster (HA)
- Attachments/Avatars: Minio (HA)
This will result in a ~ 10-pod HA setup overall.
All pods have very low resource requests.
fix #98
Co-authored-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/437
Co-authored-by: pat-s <patrick.schratz@gmail.com >
Co-committed-by: pat-s <patrick.schratz@gmail.com >
2023-07-17 19:09:42 +00:00
6814f7f6d9
bump 1.20.0
2023-07-17 01:26:32 +00:00
ca76cc571c
bump 1.19.4
2023-07-12 05:20:01 +00:00
e28c1520c0
bump to 1.19.3 ( #443 )
...
generate-chart / generate-chart-publish (push) Has been cancelled
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/443
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-05-04 09:45:36 +08:00
5876a9e7fc
Update Gitea to 1.19.2 and bump chart deps ( #442 )
...
generate-chart / generate-chart-publish (push) Has been cancelled
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
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
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
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
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
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
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
279bacb941
v1.17.4
2022-12-22 08:18:31 +08:00
6c59fe361d
v1.17.3
2022-10-17 04:19:45 +08:00
bb26a872e9
1.17.2
2022-09-07 09:21:38 +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
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
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
46b190adda
1.16.6
2022-04-21 09:03:01 +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
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
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
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
5bb91510df
Bump Gitea version to 1.15.8 ( #270 )
...
As title.
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/270
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: Gusted <gusted@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2021-12-23 03:56:36 +08:00
d97ea18626
Remove builtIn dependency values ( #268 )
...
⚠️ Breaking
Moved the values to enable the dependencies into the dependencies itself, this way we don't need a seperate field in the values and it is more obvious how to enable for example postgresql.
Co-authored-by: Lucas Hahn <lucas.hahn@novum-rgi.de >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/268
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: Andrew Thornton <art27@cantab.net >
2021-12-22 23:41:35 +08:00
3fd34a9455
1.15.4 ( #230 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/230
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Co-committed-by: techknowlogick <techknowlogick@gitea.io >
2021-10-17 00:08:17 +08:00
5a7d168c2e
1.15.3 ( #225 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/225
Reviewed-by: pat-s <pat-s@noreply.gitea.io >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Co-committed-by: techknowlogick <techknowlogick@gitea.io >
2021-09-26 08:44:59 +08:00
9a220c2ddd
1.15.0 ( #218 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/218
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 >
2021-09-12 06:40:47 +08:00
ba0e8b18b5
1.14.6 ( #212 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/212
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Co-committed-by: techknowlogick <techknowlogick@gitea.io >
2021-08-13 04:14:49 +08:00
b7dbb22025
Upgrade Gitea to 1.14.3 ( #197 )
...
Fixes : #195
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/197
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2021-06-30 23:25:56 +08:00
2901671d23
Update maintainers ( #192 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/192
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2021-06-30 03:22:46 +08:00
f344b4559d
Upgrade Gitea dependencies ( #141 )
...
- postgresql 9.7.2 to 10.3.17
- mariadb 8.0.0 to 9.3.6
- memcached 4.2.20 to 5.9.0
Tested on my clusters.
Co-authored-by: Lucas Hahn <lucas.hahn@novum-rgi.de >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/141
Reviewed-by: Andrew Thornton <art27@cantab.net >
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Co-authored-by: luhahn <luhahn@noreply.gitea.io >
Co-committed-by: luhahn <luhahn@noreply.gitea.io >
2021-06-16 05:09:02 +08:00
6e841e6e26
Fix regression for creating repositories in root-based containers ( #172 )
...
Due to #160 it was no longer possible to create repositories in root-based containers. This was caused by the missing `/tmp/gitea` directory in that image. It was dynamically created by Gitea internal functionality with less privileges than necessary.
Explicitly creating the directory and set proper permissions fix this.
Fixes : #171
Co-authored-by: JustusBunsi <sk.bunsenbrenner@gmail.com >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/172
Reviewed-by: luhahn <luhahn@noreply.gitea.io >
Reviewed-by: 6543 <6543@obermui.de >
Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io >
Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io >
2021-06-09 22:35:50 +08:00
b88bbd6d4d
gitea-1.14.x-updates ( #148 )
...
This PR includes the changes from:
- https://gitea.com/gitea/helm-chart/pulls/129
- https://gitea.com/gitea/helm-chart/pulls/140
In addition it adds the possibility to include secrets via environment variables as mentioned in #60
Co-authored-by: Hans Kristian Flaatten <hans.flaatten@evry.com >
Co-authored-by: flavio.prado <flavio.prado@noreply.gitea.io >
Co-authored-by: Lucas Hahn <lucas.hahn@novum-rgi.de >
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/148
Reviewed-by: techknowlogick <techknowlogick@gitea.io >
Reviewed-by: Andrew Thornton <art27@cantab.net >
Co-authored-by: luhahn <luhahn@noreply.gitea.io >
Co-committed-by: luhahn <luhahn@noreply.gitea.io >
2021-04-29 17:12:48 +08:00
c742b5dbc3
1.13.7 ( #139 )
...
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/139
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 >
2021-04-12 15:58:17 +08:00