zalando / zalando/postgres-operator
Disaster Recovery
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
As far as I understand, the operator boots Spilo containers which have wal-e installed. Therefore, it would be useful to be able to provide wal-e parameters to make it ship periodic backups and wal to an object store like S3.
It would be nice to be able to:
- define the log shipping target and necessary info/credentials in a secret
- define backup period to let postgres operator trigger periodic backups automatically
- define a timespan for keeping backups and wal, and the operator could delete them automatically after they are old enough
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
Review how the operator configures Spilo containers and how wal-e is exposed; the issue names no files or tests, so first map those entry points. Done means supporting secret-based log shipping credentials, scheduled backups, and retention-based cleanup for backups and WAL in an object store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- cloud, databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100