Repository navigation
feat: add pg bouncer chart - #73
Merged
Merged
Conversation
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.
PabloPardoGarcia
approved these changes
Apr 7, 2026
sudopower
force-pushed
the
sudopower/pg-bouncer-chart
branch
from
April 7, 2026 12:00
680517b to
8da442b
Compare
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.
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