gobackup / gobackup/gobackup-operator
[Restore] Support-matrix expansion (engines + backends)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 23
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Part of #81. Depends on #92, #93.
Summary
Extend the restore runner and Restore CRD beyond PostgreSQL/S3.
Scope
- Engines: MySQL/MariaDB (
mysql), MongoDB (mongorestore), Redis, etcd. - Backends: GCS and Azure download.
- Published, enforced support matrix with fail-fast validation for unsupported engine/backend combinations.
- Corresponding client binaries added to the runner image (kept minimal).
Acceptance criteria
- Documented support matrix; each supported engine has an e2e restore.
- Unsupported combinations rejected up front with a clear message.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Restore CRD and restore runner, then review prerequisite issues #92 and #93 and parent issue #81. Done means a published support matrix, upfront rejection of unsupported engine/backend combinations, minimal runner binaries, and an end-to-end restore for each supported engine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, gcp, go, kubernetes, mariadb, mongodb, mysql, redis
- Domain
- backend, cloud, databases, devops, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100