PgBouncer integration should auto-configure metadata connection · apache/airflow#54875

Repository metrics

Stars: (44,809 stars)
PR merge metrics: (平均マージ 7d 18h) (30d で 834 merged PRs)

説明

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