Next Major Release: v7

[wrenix]

Let here collect all changes for the next major release.

Solve:

• redis

• postgresql

  • issue Feature: Update postgresql 17 #641
  • additional PR chore: upgrade postgresql to 17.2 (chart 16.3.1) #642

• mariadb

  • issue: Update mariadb helm chart to 20.0.0 / breaking changes #658

• nextcloud (v31 - needed by postgresql v17)

  • version exists: tracked in https://github.com/nextcloud/server/milestone/280
  • image exists: https://hub.docker.com/_/nextcloud/tags?name=31.0.0

  ---

  maybe also:

  • Set nextcloud.podSecurityContext.fsGroup to 33 by default and allow users to configure it if needed. #379

[provokateurin]

👀

[wrenix]

On mariadb we have an updat from v18 to v20, so there are two major releases in semantic version with two breaking changes

[GreyXor]

hi @wrenix , v31.0.0 is available in docker hub

[wrenix]

So ready to merge ;)

[provokateurin]

It would be great if someone could also test the updated subcharts. It would be bad to update them to a version that is broken for some reason.

[wrenix]

i run it with redis (without database / external) .

Therefore we have the Lint and Tests.

with my other patches:

• feat(metrics): add prometheus rules (and update exporter) #694
• feat(nextcloud): add notify_push support #581

see: https://github.com/wrenix/nextcloud-helm/commits/main/

[rafal11ck]

Just want to say that when I set image to 31 I couldn't install apps and got following error in browser console when trying:

Content-Security-Policy: The page’s settings blocked the loading of a resource (connect-src) at https://<redacted>/apps/files/ because it violates the following directive: “connect-src 'self'”

I used chart version 6.6.6. I don't know if that'll be same after this PR. I removed tag image.tag wiped everything and checked with old version (30 from chart) and I can install apps from GUI.

I use(d) external postgres and no memcache for now.

[wrenix]

I could verify that bug and created an Issue upstream:
nextcloud/server#51213

It looks like an error in http <-> https location handling, which couse the problem of not being self in Content-Security-Policy way ... - lets track it in the issue.