Default database in helm chart is mysql resulting in CrashLoopBackoff - sqlite3 is needed to start container successfully
Opened this issue · 0 comments
ehlowr0ld commented
Describe the bug (must be provided)
The container is hanging in CrashLoopBackoff if you simply deplyo the chard.
Configmap must be changed to user database_type sqlite3 to start cleanly in ubernetes env.
Alternatively a mysql mus be deployed and the address adjusted in configmap - which is not very hands-free way like you would expect from helm chart.
A parameter in values.yml would be useful.
Your Environments (must be provided)
- OS: Linux / Kubernetes / Helm
- Node-version: shipped version in container image
- Studio-version: 3.10.0, master
How To Reproduce(must be provided)
Steps to reproduce the behavior:
- Deploy the chart
Expected behavior
Container starts
Additional context
Provide logs and configs, or any other context to trace the problem.