PGX + Conn Pool + Kube

Hi, n00b question here:

What is the recommended best practice for handling connection pooling with kube (so multiple containers all using the same DB)?

`pgx` obviously has its own lightweight connection pool. Should DB access still be fronted with `pgbouncer`?

Seems somewhat clunky to have to define the application connection limits for 1 container based on your knowledge of how many other containers are also using that same DB... is there an elegant solution to this?

No repository file, test, or entry point is named. Start by reviewing pgx's connection-pooling guidance and the interaction between its pool, PgBouncer, and Kubernetes containers; done would be a project-specific recommendation for managing shared database connection limits.

Written by the indexing model from the issue text.