Open baznikin opened 4 months ago
Hello! This is really useful settings for configuration application's connection to pgbouncer much fluently.
I fixed this using a custom docker image
FROM registry.opensource.zalan.do/acid/pgbouncer:master-32
RUN sed -i '/#/!s/\(server_tls_sslmode[[:space:]]*=[[:space:]]*\)\(.*\)/\1prefer/' /etc/pgbouncer/pgbouncer.ini.tmpl
RUN sed -i '/#/!s/\(client_tls_sslmode[[:space:]]*=[[:space:]]*\)\(.*\)/\1prefer/' /etc/pgbouncer/pgbouncer.ini.tmpl
values.yaml
configConnectionPooler:
connection_pooler_image: registry.local/pgbouncer:master-32.2
Operator allow to create cluster without enforced secure connections, but bundled pgBouncer enforce it.
We set
ALLOW_NOSSL: "true"
for our clusters via ConfigMap and now we want to use connection pooler. However it is enforce secure connections:Please, make it configurable or allow insecure connections with looser restrictions:
It is backward compatible with existent configurations and do not harm anyone