zalando / zalando/postgres-operator
give names to postgresql/patroni/operator port
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.8.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? STACKIT Kubernetes Engine SKE
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
We'd like to fetch the metrics provided by patroni under /metrics in the DB instance pod via prometheus. We're using the prometheus-operator and so are limited to the CRD for podMonitor or serviceMonitor to define scrape targets.
Sadly they only allow to configure scrape targets via port names not numbers. So to be able to scrape patroni metrics i'd like to add meaningful names to the ports of the postgresql-pod for patroni at least.
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 locating the configuration that defines the PostgreSQL database pod's ports, then review how the operator exposes Patroni's /metrics endpoint. Verify that the relevant port has a meaningful name accepted by prometheus-operator PodMonitor or ServiceMonitor configuration, and confirm the named target can be scraped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql, prometheus
- Domain
- databases, devops, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100