Repository navigation
ETL-782: Introduce PGBouncer for PostgreSQL connection pooling - #69
Merged
sudopower merged 2 commits intoApr 14, 2026
Merged
Conversation
The pre-install/pre-upgrade hook was unconditionally generating a new UUID on every helm upgrade, overwriting the existing installation ID in the secret and sending a spurious helm_install event. The fix reads the existing secret upfront so the ID is reused on upgrades and only generated fresh on first install.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Introduces PGBouncer as an optional connection pooler for the internal PostgreSQL deployment. Addresses connection exhaustion when many pipeline component replicas each maintain their own connection pool to Postgres (particularly relevant with schema evolution, where every ingestor/sink connects to Postgres to fetch schemas).
charts/pgbouncer/(bitnami/pgbouncer, v0.1.0) — transaction pooling by default, fully configurableglobal.pgbouncer.enabled=true,connection-urlin theglassflow-postgresqlsecret points to PGBouncer; original Postgres URL stored indirect-connection-urlpgbouncersubchart dependency andpgbouncer:config section; DB migration init container automatically usesdirect-connection-url(bypasses PGBouncer) when enabledhelm dependency updateso new subchart versions resolve in the same PR as the parent chartHow it works
PGBouncer is transparent to all components:
glassflow-postgresql/connection-urlas before — it now points to PGBouncer when enableddirect-connection-urlUsage
For external PostgreSQL users: manage your own connection pooler and point
global.postgres.connection_urlto it directly.Backward compatibility
global.pgbouncer.enableddefaults tofalse. Zero impact on existing deployments.Closes ETL-782