Merge branch '1090-work-around-trusted_domains-not-always-being-set' into 'main'

Resolve "Work around `trusted_domains` not always being set"

Closes #1090

See merge request !451

CHANGELOG.md

 # Changelog
 
+## Unreleased
+
+* Set `trusted_domains` setting explicitly in our config.
+
 ## [0.15.5] - 2022-11-09
 
 * Update nextcloud helm chart to 3.3.3.

templates/nextcloud-onlyoffice-config.yaml

@@ -172,6 +172,10 @@ data:
   #   to be trusted. 10.42.0.0/16 contains all ip addresses that are
   #   assigned to kubernetes pods, which includes the ip address of
   #   the ingress controller that functions as a reverse proxy.
+  # system.trusted_domains is actually also set by the nextcloud docker
+  #   entrypoint script from the `NEXTCLOUD_TRUSTED_DOMAINS` env var which we
+  #   also set, but that fails sometimes for unknown reasons, so we also set it
+  #   here.
   # system.overwriteprotocol overwrites the protocol of links that are
   #   generated by nextcloud to HTTPS.
   # apps.core.backgroundjobs_mode set to cron disables the unreliable ajax
@@ -182,6 +186,7 @@ data:
     {
         "system":{
             "trusted_proxies": ["10.42.0.0/16"],
+            "trusted_domains": ["localhost", {{ .Values.nextcloud.nextcloud.host | quote }}],
             "overwriteprotocol": "https",
             "appstoreenabled": false,
             "debug": {{ .Values.nextcloud.debug | quote }}