-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Chart: PgBouncer service enhancements #19749
Chart: PgBouncer service enhancements #19749
Conversation
@pgvishnuram Can you rebase on main branch & resolve conflicts please |
okay sure . let me re-verify them |
* Added support for extraVolumes and Volumemounts * Added seperate sslmode for metrics exporter * Fixed condition for pgbouncer volume mounts * Added test cases
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
3f171ba
to
d35199c
Compare
The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Problem:
pgbouncer does not support additional volume and volume mounts this lacks feature to add client side tls certificates.
Additionally pgbouncer MetricExporter sslmode is hardcoded at all times, this breaks if user tries to set sslmode=require
How does this PR fix the problem above:
This PR below functionality to solve above issues
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.