-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Feature/add pgbouncer and statsd ingress #41759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/add pgbouncer and statsd ingress #41759
Conversation
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@romsharon98 overall the changes look good. Could you add test cases for default values?
Most of the default values are set to |
On second thought, this is OK. No point of testing empty values |
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM +1
@jedcunningham WDYT?
a607505 to
466cadd
Compare
* add pgbouncer and statsd ingress * convert pgbouncer to PgBouncer * improve tests, rename flower * change ports * fix tests
* add pgbouncer and statsd ingress * convert pgbouncer to PgBouncer * improve tests, rename flower * change ports * fix tests
Today pgbouncer and statsd expose /metrics route but we cannot access it outside the cluster.
This PR adds an ingress to pgbouncer and statsd (same as webUI and flower)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.