zalando / zalando/postgres-operator
Logical backup webhook on success (or failure)
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? e.g. ghcr.io/zalando/postgres-operator:v2.0.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
I'm using Uptime Kuma together with AutoKuma for automatic monitoring. It has a fancy feature of declaring "push" monitors, where a certain webhook must be reached at least once every N seconds. This is great for backups, so you can check that at least one is being done 1 per day, per hour or whatever you want.
Now, since this operator configures logical backups, would it be possible to include support for Kuma (just a webhook) when a backup is done?
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 file or test is named. Start by locating the logical-backup configuration and execution path in the operator, then identify how a Kuma webhook could be configured and invoked. Done should include documented webhook behavior for successful backups, and clarify whether failure notifications are also supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100