You've already forked helm-gitea
Upgrade mariadb Helm chart to 8.0.0 (#48)
Upgrade mariadb Helm chart to 8.0.0
The names of the values changed in the new Helm chart, see [1]. Thus the
Helm chart ships breaking changes and therefore bump the major version
of this Chart.yaml (not sure if you use semver?)
Furthermore, there is a bug [2] where not setting the root password
results in the mariadb entering a CrashLoopBackOff when re-installing
it. Thus set it (as done in the mysql values already).
[1] 1206942b69
[2] https://github.com/bitnami/charts/issues/3884
Co-authored-by: Andre Schröder <andre.schroedr@gmail.com>
Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/48
Reviewed-by: Andrew Thornton <art27@cantab.net>
Reviewed-by: luhahn <luhahn@noreply.gitea.io>
Co-Authored-By: schra <schra@noreply.gitea.io>
Co-Committed-By: schra <schra@noreply.gitea.io>
This commit is contained in:
11
README.md
11
README.md
@ -336,8 +336,9 @@ The following parameters are the defaults set by this chart
|
||||
|
||||
| Parameter | Description | Default |
|
||||
|---------------------|-----------------------------------|------------------------------|
|
||||
|mariadb.db.user |Username of new user to create.|gitea|
|
||||
|mariadb.db.password|Password for the new user. Ignored if existing secret is provided|gitea|
|
||||
|mariadb.db.name|Name for new database to create.|gitea|
|
||||
|mariadb.service.port|Port to connect to mariadb service|3306|
|
||||
|mariadb.master.persistence.size|Persistence size for mysql |10Gi|
|
||||
|mariadb.auth.username|Username of new user to create.|gitea|
|
||||
|mariadb.auth.password|Password for the new user. Ignored if existing secret is provided|gitea|
|
||||
|mariadb.auth.database|Name for new database to create.|gitea|
|
||||
|mariadb.auth.rootPassword|Password for the root user.|gitea|
|
||||
|mariadb.primary.service.port|Port to connect to mariadb service|3306|
|
||||
|mariadb.primary.persistence.size|Persistence size for mariadb |10Gi|
|
||||
|
Reference in New Issue
Block a user