percona / percona/percona-postgresql-operator
allow annotations for jobs created by the operator for meshed environments
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 385
- Forks
- 83
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 39
Description
Proposal
When using the operator in a meshed environment, e.g. linkerd, the jobs will never finish, as the proxy sidecar container does not end. In consequence, the operator will never see the backup job finishing - and not allow to start new backups as former one is still "active".
This could be solved when the operator inherits / applies an annotation to the backup jobs, that will prevent the mesh injection.
Use-Case
Using the operator with backups in a service meshed environment like linkerd or istio
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
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, test, or entry point is named. Start by locating where the operator creates backup jobs and handles their completion, then determine how job annotations are applied. Done means backup jobs in Linkerd or Istio-meshed environments avoid proxy injection and can finish so subsequent backups are allowed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100