percona / percona/percona-postgresql-operator
Why should we have automatic backups via jobs in postgres?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 385
- Forks
- 83
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 39
Description
Why does Postgres create a backup job for me in a pvc of the same size as the space I used when creating the database in Kuber when creating the database? I really don't need this repo1 that was automatically created by pecona everest ui
postgresql-qii-repo1 Bound pvc-74ebed1a-5ce8-43b2-b3fb-3ed89adfe231 1Gi RWO
And also we don't have any mechanism to delete this job that has been completed?
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 reproducing database creation through the Percona Everest UI and inspect the generated backup job and postgresql-qii-repo1 PVC. Determine the intended lifecycle for completed jobs and backup storage, then document or implement the requested cleanup behavior and verify it after a backup completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100