zalando / zalando/postgres-operator
Add NodeAffinity support to LogicalBackup Job
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.7.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS K8s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
There seems to be no way currently to specify NodeAffinity for logical backup job. According to generateLogicalBackupJob(), affinity is limited to predefined PodAffinity only.
It would be nice to add PodAffinity support to backup job, just like it's possible to do for Postgres DB pods and Pooler (even if currently not working as desired - #1910 ).
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 at generateLogicalBackupJob(), which currently limits affinity to predefined PodAffinity, and compare how affinity is configured for Postgres DB pods and Pooler. Review the related discussion in #1910 and clarify whether the requested behavior is NodeAffinity or PodAffinity; done means the logical backup Job accepts and applies the intended affinity configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100