No ability to specify Liveness/Readiness probes timeout about helm-charts

[stevehipwell]

@Yrok472 I'm not sure I understand your query? If you're running the chart and it's slow then that is down to how you're running it and the choices you made when setting the values. For example running the chart in Kind using the built in H2 database would work but would be slow and unsuitable for anything other than testing. You need to look into the Docker image resource requirements for Jira (it's JVM) and PostgreSQL if you're running the sub-chart; for comparison we use 2 CPUs and 4 Gb RAM combined with an external cloud hosted DB and we will need to increase this soon.

[Yrok472]

Sometimes it take more than 10 minutes to start jira and default probes timeout restart my jira many times. I want to change default count of probes tries for my installation.

[stevehipwell]

@Yrok472 I understand. I've just released v4.0.2 with dynamic probe configuration.

[Yrok472]

Thank you! I'll try to verify.

[Yrok472]

It works :)