data-center-helm-charts
data-center-helm-charts copied to clipboard
[Suggestion] - Configure Database Connection Pool via values.yml
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 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
- [X] I agree to follow this project's Code of Conduct
@nagarajuvemula789 while your suggestion makes sense, there's a way to override the default database settings:
jira:
additionalEnvironmentVariables:
- name: ATL_DB_POOLMAXSIZE
value: "200"
and so on... You will find the complete list of available env vars at https://atlassian.github.io/data-center-helm-charts/containers/JIRA/#optional-database-settings