zalando / zalando/postgres-operator
[Question]Multiple backup endpoints at the same time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using?
registry.opensource.zalan.do/acid/postgres-operator:v1.10.1 - Where do you run it - cloud or metal? Kubernetes or OpenShift?
EKS, GKS. AKS - Are you running Postgres Operator in production?
yes - Type of issue?
Question
Hi, for better disaster recovery i would like to have two or more backup endpoints for wal-g backups. Right now everything is stored on GCS buckets. Are there any possibilites to use GCS and for example backblaze/wasabi/linode(s3-compatible resources) at the same time? Or it only works as 1 to 1? Wal-g can only push wals to one endpoint and then we need to use external replication tools like https://flexify.io/?
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
No source file, test, or entry point is named. Start by tracing how the v1.10.1 operator configures WAL-G backup destinations, then compare the current GCS-only behavior with the requested GCS and S3-compatible endpoints. Done means establishing whether multiple endpoints are supported and, if not, defining the required behavior or documenting the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud, kubernetes, postgresql
- Domain
- cloud, databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100