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

[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.

[GreyXor]

LGTM

[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.

This it can be ignored as there is declarative approach

nextcloud:
  hooks:
    before-starting: |-
      # install apps
      for appname in spreed contacts calendar user_oidc bookmarks deck
        do php occ app:install "$appname"
      done
      true

[GreyXor]

@provokateurin hello, can we merge it and tag a new version ? Or maybe we miss something?

[dankar]

Anything I can do as a user to assist in moving this forward? Maybe something to test?

The chart is still on 30.0.6 which means it lacks lots of fixes. Perhaps it's possible to move that to 30.0.10 if this is not ready?

[wrenix]

My test show it works. The server settings selfcheck is really slow.

Need a review. Ping @provokateurin

[JulesdeCube]

Hello @provokateurin,
sorry to ping you but when you think you could review this PR ?

I know that is repo is comunity driven but it's been 5 month since Nextcloud version 31 has been release and 2 week that this MR is ready.

[provokateurin]

Sorry I will not continue working on this repo.
I have not been using it myself for a while now and have no interest in maintaining it, as many people here (not anyone in this PR specifically) complain about everything that is not perfect, giving me no motivation at all to care about this anymore.
I'm sorry that this PR is stuck, but please stop pinging me anywhere in this repo as I will not do anything about it.
I hope you understand.

[JulesdeCube]

Hello,

sorry again to ping you my goal wasn't at all to be toxic or to force you to review. I wasn't just sneaking some information on when this pr could be merge.

I totally understand your don't want to maintain this repo any more and that you can be burn out out with nextcloud's community toxicity.

Can you remove you as maintainer so this don't append again ?
Also did you know witch maintainer is still active (so we can ask him a review) ?

[varet80]

It is a great work from all the team. And knowing about the difficulties we really appreciate it.
I understand also the frustrations the consumers (we) can bring sometimes.
I also understand if some contributors want to stop, due to various reasons.

In the other hand would be nice if before stoping at least deliver this great upgrade. And let people who do not appreciate keep complaining.

Any reviewer which would help this to move forward, would be great.

[varet80]

@wrenix I am interested to become a contributor/author for the nextcloud chart, as my work is 90% on these. I would be happy also to help maintain this chart.

[em-devops-team]

@wrenix - If nothing would be going on here we propably should fork the repo? - Or how can we find out active maintainers here.... just saw You already have a fork. Could You please publish Your helm charts?

[varet80]

@em-devops-team I am going to fork it on my Charts and put it for release! I need a few hours.
k8sonlab, will send the links.

[wrenix]

Lets open an issue to discuss maintainer ships ... maybe @provokateurin will add some maintainers afterward (i do not know any other maintainer with more access / employee at nextcloud).

For everyone how like to use my personal main-branch, it is build AS oci thanks to #720. But maybe the Versionnumber is not stable i like to rebase in this project if something change:
https://github.com/wrenix/nextcloud-helm/pkgs/container/nextcloud-helm%2Fnextcloud

[provokateurin]

You can find people in https://cloud.nextcloud.com/call/xs25tz5y or https://cloud.nextcloud.com/call/oefq5xvp who will be able to help you assign new maintainers.

[ojsef39]

lets goooo 🚀