Update nextcloud app version to 27.0.1

[jessebot]

Pull Request

Description of the change

Updates the default image tag to 27.0.1

Benefits

latest stable version as of yesterday

Possible drawbacks / Considerations

Still no upgrade guide. This'll be the first time I'm upgrading a production instance, so happy to write up a guide on it. Is it just setting nextcloud.update to 1? 🤔 Does that enable the auto-updater? Right now I have it set to the default, 0 and when I go to https://cloud.mydomain.com/updater/ it gives a 404, so maybe that's why? If I set it to 1 before upgrading the helm chart version, and just run a helm upgrade with the new values.yaml, will that break anything? I'll obviously take backups before this, but it would be nice to have a section of the README for this as upgrades are a common question we get in the issues.

Checklist

• DCO has been signed off on the commit.
• Chart version bumped in Chart.yaml according to semver.
• (optional) Variables are documented in the README.md

[jessebot]

oh, the 404 was because you're not supposed to upgrade that way. 🤦 ref:

• https://help.nextcloud.com/t/error-code-404-when-upgrading/166364
• https://github.com/nextcloud/docker#update-to-a-newer-version

[jessebot]

Tested the upgrade by only ticking up image.tag to 27.0.1-fpm (fpm because I'm using nginx) and then just syncing my nextcloud Argo CD app which uses this helm chart, and everything went ok except the Nextcloud News app, which isn't compatible with 27.0.1 yet. There were also some missing indices, but that was easily solved by running:

# where NEXTCLOUD_POD is *your* nextcloud pod
kubectl exec -it $NEXTCLOUD_POD -- su -s /bin/bash www-data -c "php occ db:add-missing-indices"

Maybe I should try to get the release notes file into this release so we can mention this in the release notes? 🤔 Either way, I will add an "Upgrading" section to the README and note that the web updater doesn't work with the docker image and to instead please just update the docker tag (after doing a backup). Perhaps a short backup section might also make sense. I'm currently using k8up and longhorn for my backups, but I'm sure velero users would like to contribute to that down the line as well, and backups are essential before an upgrade.

[jessebot]

Suggested change

	version: 3.5.20
	version: 3.6.1

This can also be 3.6.1 depending on if #420 get merged before this one or not.