The bundled `postgresql-ha` sub-chart was the only HA-ready database option, but it pinned us to a Bitnami chart whose images are no longer freely distributed, and it bundled repmgr and pgpool into the release. Operating a Postgres cluster through a Helm release also means the chart has to reimplement failover, backup and upgrade orchestration that a dedicated operator already solves. CloudNativePG is the de-facto standard operator for Postgres on Kubernetes and handles instance management, streaming replication, switchover and rolling upgrades itself. The operator is deliberately *not* part of this chart: cluster-scoped CRDs and controllers do not belong into an application release and would conflict with an operator that is already installed. The chart only renders the namespaced `Cluster` resource, so the operator can be managed independently. Because the operator cannot be assumed to be present, `cloudnativePG.enabled` defaults to `false`. Existing users of `postgresql` or an external database are therefore unaffected. Credentials follow the chart-wide `secrets.*` convention. Only the password is read from a Secret, because CloudNativePG requires `bootstrap.initdb.database` and `bootstrap.initdb.owner` as literals in the `Cluster` spec and cannot resolve them from a Secret. The password is injected into the `init-app-ini` container as `GITEA__database__PASSWD` instead of being written into the generated `app.ini`. BREAKING CHANGE: The `postgresql-ha` sub-chart and all `postgresql-ha.*` values have been removed. There is no in-place migration path between the two deployments: dump the database of the old `postgresql-ha` release with `pg_dump`, remove the `postgresql-ha` values, deploy the chart with `cloudnativePG.enabled=true` and restore the dump. Setting `postgresql-ha` now fails the release with a pointer to the changelog. Co-authored-by: Copilot <copilot@github.com>
49 lines
1.2 KiB
YAML
49 lines
1.2 KiB
YAML
apiVersion: v2
|
|
name: gitea
|
|
description: Gitea Helm chart for Kubernetes
|
|
type: application
|
|
version: 0.0.0
|
|
appVersion: 28.0.0
|
|
icon: https://gitea.com/assets/img/logo.svg
|
|
|
|
annotations:
|
|
artifacthub.io/links: |
|
|
- name: support
|
|
url: https://gitea.com/gitea/helm-gitea/issues
|
|
|
|
keywords:
|
|
- git
|
|
- issue tracker
|
|
- code review
|
|
- wiki
|
|
- gitea
|
|
- gogs
|
|
|
|
sources:
|
|
- https://gitea.com/gitea/helm-gitea
|
|
- https://github.com/go-gitea/gitea
|
|
- https://docker.gitea.com/gitea
|
|
|
|
maintainers:
|
|
# https://gitea.com/volker.raschek
|
|
- name: Markus Pesch
|
|
email: markus.pesch+apps@cryptic.systems
|
|
# https://gitea.com/DaanSelen
|
|
- name: Daan Selen
|
|
email: dselen@nerthus.nl
|
|
# https://gitea.com/ChristopherHX
|
|
- name: Christopher Homberger
|
|
email: christopher.homberger@web.de
|
|
|
|
dependencies:
|
|
# https://github.com/bitnami/charts/blob/main/bitnami/postgresql
|
|
- name: postgresql
|
|
repository: oci://registry-1.docker.io/bitnamicharts
|
|
version: 16.7.27
|
|
condition: postgresql.enabled
|
|
# https://github.com/bitnami/charts/blob/main/bitnami/valkey/Chart.yaml
|
|
- name: valkey
|
|
repository: https://valkey.io/valkey-helm
|
|
version: 0.10.0
|
|
condition: valkey.enabled
|