zalando / zalando/postgres-operator
Kubernetes persistent volumes for backup / restore
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS EKS
- Are you running Postgres Operator in production? no
- Type of issue? Feature request
I've been using the operator in a dev environment cluster for a bit now, and I greatly appreciate its simplicity! It's made postgresql clustering on Kubernetes a breeze! However, one feature that's missing is the ability to manage basebackups using Kubernetes persistent volumes. The WAL-G docs indicate this is a possible storage option:
https://github.com/wal-g/wal-g/blob/master/docs/STORAGES.md#file-system
Would it be feasible to add persistent volume storage as an option? Presently, I'm using MinIO whenever I need an S3-like API, but it would be nice to not have to rely on it.
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 linked WAL-G file-system storage documentation and the operator's existing basebackup configuration; the issue names no source file or test. Done means the operator can manage basebackups on Kubernetes persistent volumes without requiring an S3-compatible service such as MinIO.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100