zalando / zalando/postgres-operator
Make API server bind address configurable
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? ghcr.io/zalando/postgres-operator:v1.14.0 and older
- 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
time="2025-03-21T16:48:14Z" level=info msg="listening on :8080" pkg=apiserver
It is a requirement in our deployments to be able to bind the services to a certain interface instead of 0.0.0.0 or [::]. For security reasons it is a good practice to use localhost (127.0.0.1) as bind address.
In the current implementation of postgres-operator the port of the API server is configurable but the address is not.
It would be needed to make the address configurable too.
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 the API server entry point, identified by the pkg=apiserver log message, and trace how the existing configurable port is read and passed to the listener. Add an equivalent address setting and verify that the server can bind to a selected interface, including 127.0.0.1, while preserving the existing port behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100