zalando / zalando/postgres-operator
Connection pooler configuration
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
I'm trying to enable server_fast_close in the connection pooler, the CRD doesn't expose this.
The operator should expose more configuration options for the connection pooler directly in the CRD.
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 connection pooler configuration in the operator's CRD definitions and the code that maps CRD settings to the pooler. Check how server_fast_close is represented and look for existing configuration tests. Done means the CRD exposes the requested option and the operator applies it consistently; the broader set of options still needs definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100