You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To provide better flexibility and configurability for Jira Data Center deployments on Kubernetes, it would be beneficial to allow users to specify database connection pool sizes directly from the values.yml file.
Proposed Change
I suggest updating the dbconfig.xml template within the Helm chart to dynamically populate the <pool-min-size> and <pool-max-size> values using the values provided in values.yml.
Changes in values.yml
Add the following entries in values.yml:
database:
connectionPool:
minSize: 20 # Minimum pool size
maxSize: 100 # Maximum pool size
maxIdle: 50 # (Optional) Maximum idle connections
maxWait: 30000 # (Optional) Maximum wait time in ms
Product
Jira
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Suggestion
Background
To provide better flexibility and configurability for Jira Data Center deployments on Kubernetes, it would be beneficial to allow users to specify database connection pool sizes directly from the
values.yml
file.Proposed Change
I suggest updating the
dbconfig.xml
template within the Helm chart to dynamically populate the<pool-min-size>
and<pool-max-size>
values using the values provided invalues.yml
.Changes in
values.yml
Add the following entries in
values.yml
:database:
connectionPool:
minSize: 20 # Minimum pool size
maxSize: 100 # Maximum pool size
maxIdle: 50 # (Optional) Maximum idle connections
maxWait: 30000 # (Optional) Maximum wait time in ms
Product
Jira
Code of Conduct
The text was updated successfully, but these errors were encountered: