Hey n8n Community,
Hope you’re all doing well! We’re facing a puzzling issue with our n8n installation deployed using Docker and Kubernetes on AWS. Our setup includes a main pod, 2 webhook pods, and 2 worker pods. Here’s the problem: the pods keep restarting unexpectedly, but we can’t find any clues in the n8n logs as to why it’s happening.
Basically, everything seems fine, and then out of the blue, the pods start restarting without any clear triggers or error messages in the n8n logs. We’ve scoured the logs but haven’t been able to pinpoint the cause of these restarts.
So, we’re reaching out to the awesome n8n community for some guidance and experiences you might have had in similar situations. If any of you have encountered similar issues with n8n in a scalable Docker/Kubernetes setup or have insights to share, we’d really appreciate your help.
Here are a few specific questions we have:
- Have any of you faced challenges or known issues when deploying n8n in a scalable mode using Docker and Kubernetes on AWS?
- Is it possible that external factors like resource constraints, network instability, or interactions with other services are triggering these pod restarts?
- Do you know of any additional logs or debugging techniques that could shed light on the restart process and help us identify the root cause?
- Are there any specific configuration settings or best practices for deploying n8n in a scalable mode that we should be aware of?
- Can you recommend any tools or approaches for effectively monitoring and tracking pod restarts in a Kubernetes environment?
We’d be extremely grateful for any advice, experiences, or suggestions you can offer to help us get to the bottom of this issue. Your input will not only assist us in solving our problem but also contribute to the collective knowledge of the n8n community.
Thanks a ton for your time and support. Looking forward to hearing from you and sharing our progress on this matter.
- **n8n version: 0.222.1 **
- **Database (default: SQLite): Postgres **
- n8n EXECUTIONS_PROCESS setting own
- *Running n8n via Docker