Postgres secret with custom keys

[weisdd]

Is your feature request related to a problem? Please describe.

At the moment, when configured with PostgreSQL backend, the ingress-controller expects connection string to be stored in connection key of a Kubernetes secret.

Unfortunately, this limitation complicates setups where secret's structure is opinionated. E.g. cloudnative-pg, which is the most popular pg-operator on the market, has only these keys:

• dbname
• host
• jdbc-uri
• password
• pgpass
• port
• uri # this one follows the same structure as Pomerium expects
• user
• username

Describe the solution you'd like

CRD should be extended to allow key customization, connection should act as a default key value.

Describe alternatives you've considered

Workarounds I could think of would require third-party tools to generate or encrypt/decrypt secrets.