-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some PSQL seens to be failing #1311
Comments
Maybe you can share the postgres version and if you can get the api logs when the pod is starting that could help |
I've tried with the default postgres from Helm chart (15.2) and also with my cluster operator's (14.1). About the API logs, it return no error:
Extra detail: I had to log into the DB when using the default values and postgres to create the "terrakube" database even in the 2.21 |
Logs of the API Server initialization using the exact same helm values but with the 2.21.0 version:
|
I will try to reproduce this using the same helm chart that you mentioned above 15.2 |
Hello @gfranco-nos I tried using the following in minikube
And auth:
username: "terrakube"
password: "terrakubepassword"
database: "terrakube" I didn't see any issue with version 2.22.0 in my test with minikube LogsAPI PODLogs information:
So I am not sure how I can replicate the issue to help you, if you find a way that I can use to replicate it let me know so I can test on my side |
Bug description 🐞
I'm currently trying to deploy the 2.22 API image in my cluster, and everything came up fine, just the API Server that keeps hanging without any logs, just the startup probe failing.
Looking into the Postgres Pod logs, I've found the following message:
I've tried to downgrade to 2.21 and everything goes up and running.
Steps to reproduce
Helm install using the 2.22.0 api server image
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: