zalando / zalando/postgres-operator
To apply AWS S3(or/and any other providers) objects tags for logical backups (will help to implement lifecycle policies)
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.7.0 - **Where do you run it - cloud or metal?
Kubernetes/AWS - Are you running Postgres Operator in production?
yes - Type of issue?
feature request
Hi
As backup rotation is not provided by operator I would like to suggest feature about applying AWS S3 tags for the logical backups
That will allow to utilize S3 lifecycle policies in order to purge old backups
Right now its pretty hard to do because AWS policies can filter objects by prefix and tags only (no regex support), but backups are stored and organized in different way: spilo/<cluster_name>/<uuid>/logical_baclups/<time>.gz
would be really great to have ability to filter/purge old backups with tags
thanks in advance!
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 by locating the operator's logical backup upload path and how backups are stored under the spilo/<cluster_name>//logical_backups/.gz layout. Review how AWS S3 lifecycle policies use object tags, then determine the provider scope and configuration needed; done means logical backups receive usable tags that can be selected for retention policies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes, postgresql
- Domain
- cloud, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100