zalando / zalando/postgres-operator
Patroni Rest API authentication
Open
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? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.6.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Rancher k8
- Are you running Postgres Operator in production? [yes | no] Yes
- Type of issue? [Bug report, question, feature request, etc.] question
I would like to enable authentication for patroni rest API via the CR(as given below). Currently, I do not see an option via the CR or am I missing something?
restapi:
# listen: 127.0.0.1:8008
# connect_address: 127.0.0.1:8008
certfile: /etc/ssl/certs/ssl-cert-snakeoil.pem
keyfile: /etc/ssl/private/ssl-cert-snakeoil.key
authentication:
username: username
password: password
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
No file or test is named. Start by checking how the operator's CR represents Patroni REST API settings and whether authentication is passed into the generated configuration. Done means the requested username and password can be configured through the CR and applied to the Patroni REST API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- api, authentication, databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100