zalando / zalando/postgres-operator
[UI] Support Azure and GCP backups with UI
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? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Azure
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
At the moment, postgres-operator-ui appears to be hard coded to only work with AWS S3 buckets. It will not work with either GCP or Azure, both of which are supported by Spilo and WAL-G. GCP is supported by the postgres-operator, and that still doesn't work either.
It would be nice to have feature parity in the UI for both GCP and Azure.
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 in the postgres-operator-ui backup configuration flow and compare its AWS S3 handling with the provider support described for Spilo and WAL-G. Check how the postgres-operator exposes GCP support, then define done as equivalent UI backup support for both GCP and Azure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, gcp, go, kubernetes, postgresql
- Domain
- cloud, databases, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100