Breaking Change in PostgreSQL dependency

[Pumba98]

Hi, you updated the postgresql subchart to version 11. That version has some breaking changes in the values.yaml and also changes the default PostgreSQL Version from 11 to 14.
Please see https://docs.bitnami.com/kubernetes/infrastructure/postgresql/administration/upgrade/
At least the proposed values in your values.yaml need to be adjusted to fit the new chart version.

Greets 😄

[Pumba98]

I think the biggest part of this issue was fixed in #227
There still exists a problem for people who want to upgrade the nextcloud chart because the migration from PostgreSQL 11 to 14 doesn't work without manual work and recreation of the postgresql secret and statefulset is necessary.

[bo0ts]

An incompatible database upgrade (with a change in persistence no less) is no what I expected to find in a minor version bump and I would have appreciated a warning in the readme or changelogs.

[tvories]

Agreed, this should have been a major version bump. It would be nice to get a changelog setup as well as a way for the release info to pull in changes to the release. If someone has an idea on how to add change info to the release action, that would be helpful

[jessebot]

If someone has an idea on how to add change info to the release action, that would be helpful

This has been done!

@Pumba98 sorry for the inconvenience on this. 🙇 In #602 we're publishing some new guidelines to ensure we're better about this in the future, and we've also added some new tests to actually test installs with PostgreSQL enabled, so we catch breaking changes in the subchart as well:

helm/.github/workflows/lint-test.yaml

Line 73 in bf6cc4a

# test the helm chart with postgresql subchart enabled

Since we've hopefully set some better guidelines for the future to prevent this issue, and there's not been activity here for a couple of years, I'll get this closed for now.