arrstack: S3 buckets + wiring for app backups and sonarr MediaCover #389
Reference in New Issue
Block a user
Delete Branch "benvin/arrstack-s3-buckets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Servarr backups (periodic config+DB zips) and sonarr MediaCover posters still live on each replica's local
/configemptyDir: backups are leader-local and lost on reschedule, and sonarr covers render inconsistently across the 3 active-active replicas. #387 moved radarr covers to a shared Ceph RGW bucket; this extends that pattern to backups for all three apps and to sonarr's covers.Changes
arrstack-backupsObjectStoreUser + Bucket (cephrgw-operator); the operator mints thearrstack-backups-s3credential Secret in-namespace (AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / S3_ENDPOINT), so no Vault KV seeding is required. Backups get their own bucket (notarrstack-media) because they carry secrets (Config.xml API keys, the DB) and warrant separate credentials/lifecycle from poster art; the three apps share it, isolated by a per-app key prefix.arrstack-mediabucket viaSonarr__MediaCoverS3__*(prefixsonarr, partitioned from radarr'sradarrprefix to avoid movie/series id collisions), plus the estate CA mount at/etc/ssl/vault-ca/ca.crtfor RGW TLS validation.<App>__BackupS3__*toarrstack-backups(per-app prefix); add the CA mount to sonarr and prowlarr.Notes
kubectl kustomize apps/base/arrstackbuilds clean.