feat: Bump to 35.0.1 of nextcloud and migrate to Silo from Minio (#889)

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Signed-off-by: V. Aretakis <[email protected]>

feat(nextcloud): allow suspending the cron CronJob via values (#881)

* feat(nextcloud): allow suspending the cron CronJob via values

The CronJob template renders no `spec.suspend`, so the field has no
desired value in the manifest. Anything that reconciles the chart's
output — ArgoCD, Flux, `helm diff` — has nothing to compare against, and
a `kubectl patch ... suspend=true` therefore survives every subsequent
sync while the release keeps reporting as in-sync.

That is not hypothetical: we had `nextcloud-cron` suspended by hand
during a debugging session and left that way for 40 days. ArgoCD
reconciled the object repeatedly over that period and left the
suspension in place, because server-side apply correctly treats
`spec.suspend` as owned by the client that set it. No file scans, no
trashbin/version expiry, no notification delivery and no federated sync
ran in that window, and nothing surfaced it.

Render `suspend` unconditionally, defaulting to false, so the field is
always present and always owned by whatever applies the chart. This also
makes suspending the job a first-class values option rather than
something you have to reach around the chart to do.

Default behaviour is unchanged: `suspend: false` is the CronJob API
default, so existing releases render an explicit false where the field
was previously omitted.

Signed-off-by: Marek Jagielski <[email protected]>

* feat(nextcloud): take the suspend default from values.yaml alone

`values.yaml` already declares `cronjob.cronjob.suspend: false`, so the
`| default false` pipeline in the template held a second copy of the
same default that could never actually fire — Helm merges the chart
defaults under any user-supplied values before the template runs.

Drop it, matching the surrounding fields in the same block
(`successfulJobsHistoryLimit`, `failedJobsHistoryLimit`), which read
their values straight through.

Rendering is unchanged: `suspend: false` by default, `suspend: true`
with `--set cronjob.cronjob.suspend=true`.

Signed-off-by: Marek Jagielski <[email protected]>

---------

Signed-off-by: Marek Jagielski <[email protected]>
Signed-off-by: WrenIX <[email protected]>
Co-authored-by: WrenIX <[email protected]>

fix(nextcloud): update AppVersion to v34.0.4 #884

Signed-off-by: Adrian Nöthlich <[email protected]>

fix(nextcloud): update AppVersion to v34.0.3 #880

Signed-off-by: Adrian Nöthlich <[email protected]>

Merge pull request #873 from promasu/bump-nextcloud

chore(deps): update docker.io/library/nextcloud docker tag to 34.0.2

Merge pull request #872 from sapslaj/fix-nil-pointer-evaluating-with-…

…cronjob-enabled

fix: nil pointer when evaluating when cronjob.enabled=true

Merge pull request #752 from antoinetran/feature/issue187-fixredisper…

…mission_nextcloud7

Fix #187: fix redis-session.ini permission denied

Merge pull request #866 from somaz94/feat/httproute-well-known-redirects

feat(nextcloud): add CalDAV/CardDAV redirects to HTTPRoute

Merge pull request #868 from somaz94/fix/httproute-argo-drift

fix(nextcloud): add explicit group/kind to HTTPRoute backendRefs to prevent Argo CD drift

feat(nextcloud): update AppVersion to v34.0.1 #865

Signed-off-by: WrenIX <[email protected]>