percona / percona/percona-postgresql-operator

Being able to create or import PgBouncer users through the PerconaPGCluster CR

Open
#1,169 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

jira-task v2.10.0
Dominant language
Go
Stars
385
Forks
83
Avg merge
2d 5h
Merged PRs (30d)
39

Description

Proposal

At the moment, the operator creates only one user _crunchypgbouncer in the users.txt file for PgBouncer. We would benefit from being able to create our own users with the right set of permissions,

Either of these options would work:

  1. Being able to create users for PgBouncer in the proxy config in the PerconaPGCluster the same way it is done for PostgreSQL in the users section.
  2. Being able to propagate roles created in the users section to PgBouncer.
Use-Case

This would allow us to use the PgBouncer metrics exporter with a user that has the appropriate permissions.

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the PerconaPGCluster CR's users section is translated into PostgreSQL roles and how the PgBouncer users.txt file is generated. Compare the two proposed approaches and determine which configuration path can support the metrics exporter; done means the CR can provision or propagate an appropriately permissioned PgBouncer user.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.