zalando / zalando/postgres-operator
Custom labels for pooler
Open
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? postgres-operator:v1.9.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Kubernetes
- Are you running Postgres Operator in production? [yes]
- Type of issue? [question]
I configured inherited_labels with my custom label and it works. But it doesn't add my custom label to pooler pod.
Do I do something wrong maybe?
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 tracing how the inherited_labels configuration is applied and how pooler pods are created, then compare that with the path where the custom label already works. Done means a configured custom label is present on the pooler pod as well, with the behavior verified in the relevant Kubernetes setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100