Fix triggerer KEDA database connection rendering#67538
Merged
Merged
Conversation
henry3260
requested review from
bugraoz93,
hussein-awala,
jedcunningham and
jscheffl
as code owners
henry3260
force-pushed
the
triggerer-keda-db-conn
branch
from
d96705b to
a7e8c5b
Compare
henry3260
force-pushed
the
triggerer-keda-db-conn
branch
from
a7e8c5b to
f19eaf3
Compare
jscheffl
approved these changes
May 26, 2026
jscheffl
added
the
backport-to-chart/v1-2x-test
Contributor
Backport successfully created: chart/v1-2x-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
jscheffl
pushed a commit
that referenced
this pull request
May 26, 2026
Contributor
Backport successfully created: chart/v1-2x-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
29 tasks
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
2 participants
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.
Why
Triggerer KEDA can require
KEDA_DB_CONNwhen using a MySQL metadata database, or when PgBouncer isenabled but
triggerer.keda.usePgbouncer=false.Before this change, the chart only rendered
KEDA_DB_CONNand the metadata Secret'skedaConnectionbased on worker KEDA conditions. As a result, deployments with triggerer KEDA enabled but worker KEDA
disabled could render a ScaledObject that references
KEDA_DB_CONN, while the triggerer container andmetadata Secret did not provide it.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.