-
-
Notifications
You must be signed in to change notification settings - Fork 351
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
[Bug]: Traefik keeps restarting all the time #1500
Comments
It appears that setting
And I had 0 agent nodes, but 2-4 autoscaled nodes. Probably a single pod with traefik couldn't handle the amount of traffic apps on my cluster were getting, though I am going to leave this issue open until it's confirmed to be a misconfiguration on my side and not an actual bug. |
Description
I have created a new cluster recently and deployed a couple of web services there along with TLS for each one of them. And finally I put the Hetzner LB behind CloudFlare. And that's when I started getting 525 SSL Handshake Error from CloudFlare. Investigation led me to
traefik
pod logs which shows that traefik is being restarted quite a lot and I can't seem to understart a true reason behind it.Then I execute this command in terminal again after a couple of minutes
For some reason,
traefik
jumps from node to node.Then I looked into traefik logs and here what it shows
Traefik logs
It just shuts down gracefuly and that's it. So I kept monitoring it and sometimes I get additional errors
use of closed network connection
:I thought maybe this could happen because I have 0
agent_nodepools
nodes, only autoscaled ones, where I already deployed high traffic web apps that could easily consume a lof of CPU and RAM. I've added a new node to the agent just to make sure, and traefik pod did occupy that spare node, yet restarted again.I'm completely out of ideas at this point. Traefik is not crashing, it just keeps restarting. Traefik docs says that the stop signal comes from above.
Kube.tf file
Screenshots
No response
Platform
Linux
The text was updated successfully, but these errors were encountered: