Add trusted_domains after installation

[denppa]

Installed Nextcloud via helm on a baremetal k8s cluster. Created an ingress from another domain to point to Nextcloud service, but it won't let me visit the site because of a trusted_domain error.

Went back into values.yml and added the new domain, ran:

helm upgrade -n nextcloud nextcloud/nextcloud --values values.yml

However, the config.php did not reflect the new list of trusted domains after restart.

Relevent values.yml

  trustedDomains:
    - nextcloud.mydomain.com
    - nextcloud.mydomain2.com

mydomain2.com is the new domain, did not get added to config.php.

[jessebot]

hmmm, not sure if the way we set the trusted domain is parsed a second time after installation, but can you try running the occ command to update it?

It should be something like:

kubectl exec -it your-nextcloud-pod -- /bin/sh -c "php occ config:system:set trusted_domains 2 --value=nextcloud.mydomain2.com"

[denppa]

hmmm, not sure if the way we set the trusted domain is parsed a second time after installation, but can you try running the occ command to update it?

It should be something like:

kubectl exec -it your-nextcloud-pod -- /bin/sh -c "php occ config:system:set trusted_domains 2 --value=nextcloud.mydomain2.com"

This is the solution. Would be great if the documentation can mention that certain params inside values.yml will need to be changed manually after deployment.

[jessebot]

This is the solution.

Ok, good, glad it's at least not a blocker 🙏

Would be great if the documentation can mention that certain params inside values.yml will need to be changed manually after deployment.

Sure, we're open to PRs for this in the README here:
https://github.com/nextcloud/helm/tree/main/charts/nextcloud

[AlbaCI]

Hi! I’m going to work on solving this issue by improving the README with a note about post-deployment parameter changes.
I’ll make a PR once it’s ready.

Thanks!
Alba

[AlbaCI]

Hi! I’ve completed the changes and opened a PR: #849