You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 14, 2025. It is now read-only.
@@ -494,6 +500,73 @@ The nextcloud deployment includes a series of different probes you can use to de
494
500
> [!Note]
495
501
> If you are getting errors on initialization (such as `Fatal error: require_once(): Failed opening required '/var/www/html/lib/versioncheck.php'`, but you can get other errors as well), a good first step is to try and enable the startupProbe and/or increase the `initialDelaySeconds` for the `livenessProbe` and `readinessProbe` to something much greater (consider using `120` seconds instead of `10`. This is an especially good idea if your cluster is running on older hardware, has a slow internet connection, or you're using a slower storage class, such as NFS that's running with older disks or a slow connection.
496
502
503
+
### Collabora Configuration
504
+
505
+
This section provides options to enable and configure the Collabora Online server within your deployment. Please ensure to review the [Collabora Online Helm chart documentation](https://github.com/CollaboraOnline/online/tree/master/kubernetes/helm/collabora-online) for additional details and recommended values.
| `collabora.ingress.enabled` | Enable or disable ingress for Collabora Online | `false` |
521
+
| `collabora.ingress.className` | Class name for the ingress controller | `""` |
522
+
| `collabora.ingress.annotations` | Annotations for the ingress resource | `{}` |
523
+
| `collabora.ingress.hosts` | List of hosts for the Collabora ingress | `[{"host": "chart-example.local", "paths": [{"path": "/", "pathType": "ImplementationSpecific"}]}]` |
524
+
| `collabora.ingress.tls` | TLS configuration for the Collabora ingress | `[]` |
525
+
| `collabora.resources` | Resource requests and limits for the Collabora Online pods | `{}` |
526
+
> **Note**:
527
+
>
528
+
> You may need to uncomment `collabora.collabora.aliasgroups` and `collabora.collabora.extra_params`, depending on your setup. You may also need to set `collabora.collabora.server_name`. If left empty, it's derived from the request, so please set it if it doesn't work.
529
+
>
530
+
> If you have both Nextcloud and Collabora behind a reverse proxy with HTTPS, `collabora.collabora.aliasgroups` should match your Nextcloud domain and `collabora.collabora.server_name` (if needed) should match your Collabora domain.
531
+
>
532
+
> For more information, please check the [Collabora documentation](https://sdk.collaboraonline.com/docs/installation/index.html).
533
+
534
+
### Imaginary
535
+
536
+
We include an optional external preview provider from [h2non/imaginary](https://github.com/h2non/imaginary).
| `imaginary.securityContext` | Optional security context for the Imaginary container | `nil` |
551
+
| `imaginary.podSecurityContext` | Optional security context for the Imaginary pod (applies to all containers in the pod) | `nil` |
552
+
| `imaginary.service.type` | Imaginary: Kubernetes Service type | `ClusterIP` |
553
+
| `imaginary.service.loadBalancerIP` | Imaginary: LoadBalancerIp for service type LoadBalancer | `nil` |
554
+
| `imaginary.service.nodePort` | Imaginary: NodePort for service type NodePort | `nil` |
555
+
| `imaginary.service.annotations` | Additional annotations for service imaginary | `{}` |
556
+
| `imaginary.service.labels` | Additional labels for service imaginary | `{}` |
557
+
558
+
559
+
> [!Note]
560
+
> You also need to setup nextcloud, to use imaginary
561
+
```yaml
562
+
nextcloud:
563
+
defaultConfigs:
564
+
imaginary.config.php: true
565
+
566
+
imaginary:
567
+
enabled: true
568
+
```
569
+
497
570
## Cron jobs
498
571
499
572
To execute [background tasks](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html) by using system cron instead of default Ajax cron, set `cronjob.enabled` parameter to `true`. Background jobs are important for tasks that do not necessarily need user intervention, but still need to be executed frequently (cleaning up, sending some notifications, pulling RSS feeds, etc.).
0 commit comments