MIgration fail due to liveness prove timeout
Opened this issue · 0 comments
sebglon commented
Helm chart 2.16.5
if the migration is not termintated before the end of the liveness initialDelaySeconds, the pod restart and the next run fail with error:
database has migration lock; cannot run migrations.
Workarround is to manually increase the initialDelaySeconds.
Solution can be to use the k8s startup probe