zalando / zalando/postgres-operator
How to configure x509 based authentication/authorization against Pooler/Bouncer/PG-instance
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?
- ghcr.io/zalando/postgres-operator:v1.13.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift?
- Kubernetes
- Are you running Postgres Operator in production? [yes | no]
- Yes
- Type of issue? [Bug report, question, feature request, etc.]
- Question/Documentation
To improve the security posture of our PG deployment, we would like to enable and configure Certificate Authentication.
I was able to find encryption related docs, but not how to configure Pooler/Bouncer or the PG-instances to enable authenticating/authorizing clients based on their x509 certificates.
Please advise,
Thank you
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 docs/user.md at the custom TLS certificates section and the linked PostgreSQL certificate-authentication documentation. Compare the documented configuration with what is needed for PostgreSQL instances and Pooler/Bouncer. Done means documenting the supported authentication and authorization setup, or clearly stating that a requested component is unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- authentication, databases, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100