Upgrade mariadb Helm chart to 8.0.0 #48

2020-10-20T16:35:39Z

schra commented

2020-10-20 16:35:39 +00:00

(Migrated from gitea.com)

This PR superceeds #46, which was destroyed in the server migration ("schra wants to merge 0 commits from <deleted>:update-mariadb into master")

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

This PR superceeds #46, which was destroyed in the server migration ("schra wants to merge 0 commits from \<deleted\>:update-mariadb into master") --- 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] https://github.com/bitnami/charts/commit/1206942b69c02a140a60e4e5ab59bf6d53d5b7e6 [2] https://github.com/bitnami/charts/issues/3884

👍 1

luhahn commented

2020-10-20 17:12:18 +00:00

(Migrated from gitea.com)

Thanks for readding, will test tomorrow :)

zeripath (Migrated from gitea.com) approved these changes 2020-10-21 08:06:32 +00:00

luhahn (Migrated from gitea.com) approved these changes 2020-10-21 13:02:49 +00:00

luhahn (Migrated from gitea.com) left a comment

looks good & tested on my clusters

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lunny/helm-chart#48