Deployed helm chart to kubernetes. Api pod fails to start. No error message to work with:(
brandoncollins7 opened this issue · 4 comments
@brandoncollins7 we need more information here please. Can you let us know which versions of the helm chart and flagsmith images you're using? If you can also provide as much of your values.yaml file as you're happy to share that would be very helpful as well. Thanks!
I am using latest. Simply followed these steps on the docs page:
helm repo add flagsmith https://flagsmith.github.io/flagsmith-charts/
helm install -n flagsmith --create-namespace flagsmith flagsmith/flagsmith
I believe it has something to do with not finding a database. Looks like there wasn't any postgres deployed?
Hello @brandoncollins7! Just tried reproducing by running the exact commands you provided. I did get the Error from server (BadRequest): container "flagsmith-api" in pod "flagsmith-fresh-test-api-87d8745c6-q4nqj" is waiting to start: PodInitializing message while the API pod was initializing, but it eventually was up and running, just as expected.
If your API pod is stuck in this state, this means the init containers take too much time to run. To check the status of init containers, please select the wait-for-db/migrate-db container in your UI or use the following commands:
kubectl logs -l 'app.kubernetes.io/component=api' -c wait-for-db
kubectl logs -l 'app.kubernetes.io/component=api' -c migrate-db @brandoncollins7 We didn't hear back from you so I'm closing this issue. Feel free to come back with details and we'll reopen it should we reproduce a problem.