Why is Traefik Using So Much CPU and Memory in My Homelab?

UPDATE: I figured out what was causing the strain! By increasing the verbosity for Traefik, I noticed a lot of 404 and 502 errors linked to my Matrix Synapse ingresses. Once I deleted those, the resource usage dropped drastically. The issue stemmed from the handling of targetPort for external name services—it needed adjustments to work properly with Traefik. After fixing that and re-applying the correct service settings, everything is back to normal (mostly, aside from a few TLS errors due to missing annotations).

If you want to dig deeper into what's causing the spike, profiling could help pinpoint the trouble spots. But how do you even go about profiling something like this? Would toggling options in the logs work, or do you have specific tools in mind?

From what I've seen, Traefik can be a bit aggressive with memory usage, often consuming whatever is available to keep GC loads low. Try limiting its resource allocation—you might see a significant decrease in memory usage without impacting performance.

It sounds like that CPU and memory usage is way off for your setup! A couple of things to consider: you've likely got too many providers active—CRD, Ingress, and nginx migration could be causing the overload. Try disabling the kubernetesIngressNginx and see if it helps. Also, check those logs; it might be stuck in a resync loop, which could explain the high resource consumption.