dheerenmohta opened a new pull request, #71830: URL: https://github.com/apache/airflow/pull/71830
The auto-generated result-backend connection secret built the PgBouncer hostname from .Release.Name directly, omitting the namespace — unlike the already-correct sibling logic in the metadata connection secret. This silently breaks Celery result-backend to PgBouncer routing whenever useStandardNaming (the chart's own recommended setting) or fullnameOverride is used, since the rendered PgBouncer Service name diverges from .Release.Name. Derives the PgBouncer host the same way the metadata secret already does, and adds a regression test covering the useStandardNaming: true case. Note: this does not fully resolve #54875's original ask. Auto-configuring PgBouncer when the metadata connection is backed by an externally-managed, opaque Kubernetes Secret isn't something Helm templating can do, since it can't introspect that Secret's contents at render time. This fixes a real, narrower, verified bug in the chart's own auto-generated-secret path. related: #54875 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Sonnet 5) Generated-by: Claude Code (Sonnet 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
