apache/airflow

PgBouncer integration should auto-configure metadata connection

Open

#54875 opened on Aug 23, 2025

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Python (44,809 stars) (16,781 forks)batch import
area:helm-chartgood first issuekind:bug

Description

Official Helm Chart version

1.18.0 (latest released)

Apache Airflow version

3.0.2

Kubernetes Version

1.33

Helm Chart configuration

data: metadataSecretName: app-env

pgbouncer: enabled: true configSecretName: app-env metricsExporterSidecar: statsSecretName: app-env statsSecretKey: pgbouncer_exporter_connection

Docker Image customizations

No response

What happened

When enabling PgBouncer in the Airflow Helm chart by providing a pgbouncer.ini configuration, users must manually configure Values.data.metadataSecretName to customize the database connection. This requires knowing the PgBouncer service name in advance to properly configure the secret, creating a circular dependency where you need to know the generated service name before the chart is deployed.

What you think should happen instead

When PgBouncer is enabled, the Helm chart should:

Allow users to specify PostgreSQL connection details (host, database, user, password) through standard configuration values or secret references Automatically detect that PgBouncer is enabled when creating the metadata connection secret Auto-configure the connection to use the PgBouncer service instead of the direct PostgreSQL connection Eliminate the need for users to pre-configure metadataSecretName with PgBouncer-specific connection strings

The chart should handle the service name resolution and connection routing internally, making PgBouncer integration seamless.

How to reproduce

Following the official Production Guide to enable pgbouncer

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
pythonpostgresqlkubernetes
Domain
backenddatabasedevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Helm chart templatingKubernetes resourcesAirflow database connectionPgBouncer basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the Helm chart templates for PgBouncer, particularly templates/configmap.yaml and helpers for metadata connection. The issue suggests making the chart auto detect PgBouncer and adjust the metadata connection secret accordingly. Look at how the service name is generated for PgBouncer and consider using that in the metadata secret creation. Also review the production guide documentation for steps to enable PgBouncer.