schra a4e5943ca5 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>		2020-10-22 13:13:37 +08:00
..
config.yaml	Upgrade mariadb Helm chart to 8.0.0 (#48)	2020-10-22 13:13:37 +08:00
http-svc.yaml	Re-add lost commit: Enable LoadBalancer type service of http (#42) (#49)	2020-10-21 20:38:01 +08:00
ingress.yaml	Integrate NOVUM-RGI chart into the official helm chart. (#7)	2020-08-23 17:56:55 +00:00
init.yaml	Move all password related data to secrets (#28)	2020-09-25 13:37:55 +00:00
ssh-svc.yaml	Fix NodePort settings for ssh service (#32)	2020-09-28 14:31:35 +00:00
statefulset.yaml	Move all password related data to secrets (#28)	2020-09-25 13:37:55 +00:00