Skip to content

Upload backups with MinIO client instead of AWS CLI - #14

Merged
austin-barrington merged 1 commit into
mainfrom
fix/backup-minio-mc
Sep 4, 2026
Merged

austin-barrington merged 1 commit into
mainfrom
fix/backup-minio-mc

Conversation

@austin-barrington

Copy link
Copy Markdown
Member

Summary

  • Backup/restore Jobs snapshot with the HyperbyteDB image, then transfer objects with minio/mc. No AWS account and no AWS CLI in the database image.
  • Restore Job names stay under 63 bytes so Kubernetes will accept the job-name label.

Test plan

  • go test ./internal/controller/ -count=1
  • Kind: portal Back up now → MinIO upload → restore UUID → cluster Running

Made with Cursor

The database image has no AWS CLI, so Jobs that ran aws s3 sync always failed.
Use an mc sidecar against S3-compatible storage (MinIO locally) and keep restore
Job names under 63 bytes so Kubernetes will accept them.
@austin-barrington
austin-barrington merged commit d53699d into main Sep 4, 2026
4 checks passed
@austin-barrington
austin-barrington deleted the fix/backup-minio-mc branch September 4, 2026 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant