Files
cozystack/examples/backups/redis/bucket.yaml
T
Andrey Kolkov ac79c3757b test(backups): self-contained Redis backup round-trip e2e
The Redis driver shipped no round-trip backup/restore e2e, unlike its
ClickHouse, MariaDB and RabbitMQ siblings, so the backup to S3 and restore
data path had no automated coverage. The existing demo backed up through the
platform cozy-default BackupClass, whose endpoint is the shared system
bucket; in the e2e environment that bucket's advertised external address is
not routable, so a cozy-default round-trip cannot run there.

Rework examples/backups/redis to provision its OWN Bucket + Redis strategy +
BackupClass (mirroring the MariaDB and RabbitMQ demos), projecting the
bucket's keys and the seaweedfs CA into the Secrets the strategy references
and honouring an S3_ENDPOINT override so the backup Pod targets the
in-cluster seaweedfs. Add a redis-2-backup-roundtrip Chainsaw test that
drives run-all.sh in tenant-root and asserts the sentinel round-trips
through object storage in place and into a copy.

Signed-off-by: Andrey Kolkov <androndo@gmail.com>
Assisted-by: LLM
2026-09-08 17:57:06 +04:00

20 lines
773 B
YAML

# Cozystack-managed S3 bucket for storing this demo's Redis RDB snapshots.
# The Bucket controller provisions a Secret named "bucket-<bucket>-<user>" per
# user (the bucket app carries the "bucket-" release prefix); run-all.sh reads
# the "backup" user's BucketInfo and projects its access keys into the
# redis-backup-creds Secret the strategy references.
#
# The platform ships a cozy-default-redis strategy that writes to the shared
# cozy-backups system bucket; this demo instead provisions its own Bucket and a
# matching strategy so the round-trip is self-contained and its objects are torn
# down with the demo (see cleanup.sh).
---
apiVersion: apps.cozystack.io/v1alpha1
kind: Bucket
metadata:
name: redis-backups
spec:
users:
backup:
readonly: false