relution-io / relution-kubernetes Goto Github PK

I just tried out the helm chart, and it mostly seems to work great, but I had to modify the chart locally to remove the liveness probes because they were causing the pod to restart before the initial database could be setup.

Issue
Liveness probes kill the relution pod before it can finish the initial setup.
My machine is very powerful, and runs on an nVME SSD, multiple cores, and has 64Gb of ram.

Expected Result
The liveness probes should not kill the pod for inaccessibility until after setup is complete.
There should at least be some configuration options for the liveness probes available.

Steps to Reproduce
Run the helm chart with the instructions provided. Observe the relution pod restart.