Nextcloud
The nextcloud Argo Application adopts the existing Helm release nextcloud
in namespace nextcloud, using the upstream chart version selected in
bootstrap/nextcloud.yaml. Its Bitnami PostgreSQL subchart is already enabled:
the live application uses nextcloud-postgresql in this namespace, not the
shared default/postgresql. No database copy or restore was needed for this
migration. The same PostgreSQL StatefulSet and PVC remain in use.
The public values file references existing namespace Secrets for the
administrator, database, Redis, Collabora, metrics, and S3 credentials. The
S3 Secret nextcloud-objectstore was created once from the former private
values; none of those values is stored in Git. Recreate these Secrets from the
encrypted administrator backup before restoring this application in a new
cluster. The upstream chart does not render Secrets when these references are
enabled. Retain the old Helm release metadata as historical rollback data.
The Ceph nextcloud object user is adopted unchanged. Its existing bucket ID
is e326b22c-970e-4ff6-bf65-499f3bab92bf.900401.10; do not recreate,
rename, or delete the bucket. Before first sync it contained 546,072 objects.
The pre-adoption PostgreSQL dump is outside Git at
/home/feedc0de/migration-backups/nextcloud/pre-argocd-2026-10-20.dump on
the administrator host. These local files are not a substitute for off-site
backups.
Automated pruning is disabled because this release owns data-bearing PVCs and an object-store user. Nextcloud's local install script must not be run against an Argo-owned resource. Separate companion Deployments for whiteboard, Talk HPB, and ClamAV and the notify-push Service/Ingress are being migrated as their own deployment contracts; do not delete them merely because they are absent from the upstream Nextcloud chart.