zalando / zalando/postgres-operator
Patroni REST API Authentication
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi,
I understand that the Patroni REST API is exposed on each spilo pod, at port 8008. Doesn't this pose a major security risk? It seem to me that every program running on the Kubernetes cluster could issue a PATCH /conifg request to this API, and mess up each database cluster. Is it possible to configure basic HTTP authentication for the Patroni REST API endpoints (as described here) ? If yes, how can I do this; and if not, isn't this a big security problem?
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 with the linked Patroni REST API and security documentation, then trace how the postgres-operator exposes configuration for each Spilo pod. Determine whether basic HTTP authentication can be configured for the REST API and document or implement the supported approach; done means the security question has a verified, reproducible answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100