-
Notifications
You must be signed in to change notification settings - Fork 16.4k
allow pgbouncer replicas to be configurable #27439
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
allow pgbouncer replicas to be configurable #27439
Conversation
| {{- end }} | ||
| spec: | ||
| replicas: 1 | ||
| replicas: {{ .Values.pgbouncer.replicas }} |
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.
I understand that you have added the default value in the values.yaml file, but it may be good to have { ... | default 1} here too, so that it will still work in the expected way even if the values file is messed up.
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.
Okay let me add defaults in template
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.
@XD-DENG, can you expand on "even if the values file is messed up" more? If the values file shipped with the chart is messed up, we are so far from having anything working that duplicating defaults around seems like extra noise to me. Am I missing something?
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
This change allows pgbouncer replicas to be configurable and removes hardcoding of values
^ 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.