mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-14 00:23:54 +09:00
Andrey Kolkov
329ef9cf3f
The rabbitmq backup roundtrip was the only backup e2e routing through the platform cozy-default system bucket, whose advertised endpoint in the CI sandbox is the unroutable s3.example.org placeholder, so the backup Job failed with "Could not resolve host: s3.example.org". Mirror the clickhouse/mariadb backup examples: provision a demo Bucket, project its access keys into rabbitmq-backup-creds and copy the seaweedfs CA into rabbitmq-backup-ca, and render a self-contained Rabbitmq strategy + rabbitmq-default BackupClass whose curl uploads to the in-cluster seaweedfs endpoint (S3_ENDPOINT override, CURL_CA_BUNDLE for the self-signed cert). The in-Pod script is kept identical to the shipped cozy-default-rabbitmq strategy, which is left unchanged; the demo only reuses its client image. Assisted-By: LLM Signed-off-by: Andrey Kolkov <androndo@gmail.com>
19 lines
617 B
YAML
19 lines
617 B
YAML
# Maps Kind=RabbitMQ to this demo's Rabbitmq strategy. BackupClass is
|
|
# cluster-scoped, so a single instance covers every namespace. Named
|
|
# rabbitmq-default so it does not collide with the platform cozy-default class,
|
|
# which routes RabbitMQ to the shipped cozy-default-rabbitmq strategy.
|
|
---
|
|
apiVersion: backups.cozystack.io/v1alpha1
|
|
kind: BackupClass
|
|
metadata:
|
|
name: rabbitmq-default
|
|
spec:
|
|
strategies:
|
|
- application:
|
|
apiGroup: apps.cozystack.io
|
|
kind: RabbitMQ
|
|
strategyRef:
|
|
apiGroup: strategy.backups.cozystack.io
|
|
kind: Rabbitmq
|
|
name: rabbitmq-strategy-default
|