Skip to content

feat: add pg bouncer chart - #73

Merged
sudopower merged 7 commits into
mainfrom
sudopower/pg-bouncer-chart
Apr 7, 2026
Merged

sudopower merged 7 commits into
mainfrom
sudopower/pg-bouncer-chart

Conversation

@sudopower

@sudopower sudopower commented Apr 7, 2026 •

Copy link
Copy Markdown
Member

Need to be merged into main for release, not used anywhere
Merge to main should create a sub chart release which can be used in the main chart release PR

Adds PGBouncer as a new internal subchart and wires it transparently
into the existing PostgreSQL/operator/component connection flow so that
no changes are required to operator code or component images.

Why: schema evolution changes require each pipeline component to connect
to Postgres to fetch message schemas. With many replicas this overwhelms
Postgres's connection limit. PGBouncer in transaction pooling mode solves
this by sharing a small server-side connection pool across all clients.

Changes:
- charts/pgbouncer/: new internal chart (bitnami/pgbouncer, transaction
  mode by default) configurable via global.pgbouncer.enabled
- charts/postgresql/: bumped to v0.1.9; when global.pgbouncer.enabled=true
  the glassflow-postgresql secret writes the PGBouncer service URL into
  connection-url (used by API, operator, components) and keeps the direct
  Postgres URL in a new direct-connection-url key
- charts/glassflow-etl/: adds pgbouncer subchart dependency, pgbouncer
  config section in values.yaml, and routes DB migrations to
  direct-connection-url when PGBouncer is enabled
- release.yaml: pre-packages local subcharts before helm dependency update
  so new subchart versions resolve without needing a prior publish step

Enable with: helm upgrade --set global.pgbouncer.enabled=true
Default is disabled — zero impact on existing deployments.
@sudopower
sudopower force-pushed the sudopower/pg-bouncer-chart branch from 680517b to 8da442b Compare April 7, 2026 12:00
@sudopower
sudopower merged commit 0c6ebb1 into main Apr 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants