-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
pod/convoy-agent in CrashLoopBackOff without any logs #2251
Comments
Hey @kardeepakcars24, This seems like a connection error as I see an Can you try to run Convoy without the external DB and Redis so it spins up Postgres and Redis pods in the cluster? |
Thanks @jirevwe for the response. Yes, the pods can reach the RDS and Redis. Earlier there was an Auth issue, which threw an error in init container. There are many services setup in the cluster connecting to this RDS and redis. I believe the init container should crash if there is a connection issue, isn't it so? |
Based on the logs shared, the agent command failed. Can you show me the output of kubectl pods |
@jirevwe Did you perhaps mean this?
|
Thanks @jirevwe for connecting on call. Setting scheme: "redis" to scheme: "rediss" fixed the issue. Might I propose that some logging about this part on connecting to redis could help. |
I have installed convoy in EKS using the helm chart pointing to my aws rds and elasticache redis. The init container has run successfully:
This is what kubectl logs show:
wait-for-migrate container shows no logs
This is my helm chart values.yaml:
The text was updated successfully, but these errors were encountered: