Evgeny

> Are you using reloader with reloader.stakater.com/auto annotation or any other ones? we do use `reloader.stakater.com/auto` annotations only. The interesting thing is that only a couple of deployments in each...

A couple of updates: 1. CPU throttling graph looks like this: 2. I'm also trying to exclude some of the namespaces with the biggest amount of secrets and configmaps via:...

@msafwankarim I can see that you were working on the pprof support for reloader recently: https://github.com/stakater/Reloader/pull/961 this is something that could help us here as well

I checked some memory stats via ephemeral sidecar containers. Here is the data: ``` reloader-reloader-598bff4866-fxf7g:/root$ ps aux PID USER TIME COMMAND 1 nobody 6:42 /manager --reload-strategy=annotations 10 nobody 0:00 /bin/bash...

Thanks, @msafwankarim I'm going for a leave until September, a colleague of mine will be continuing the investigation from our side. We will use `pprof` and share the results here.

Hey @rasheedamir we were able to find the root cause using the latest version of reloader (`--log-level=debug` actually worked in the latest version, yay! :) ). reloader was overloaded because...

Hi, I've faced the same issue, e.g. no debug messages with `reloader` v 1.10 and kubernetes v1.31.6: ``` time="2025-07-21T13:54:25Z" level=info msg="Environment: Kubernetes" time="2025-07-21T13:54:25Z" level=info msg="Starting Reloader" time="2025-07-21T13:54:25Z" level=warning msg="KUBERNETES_NAMESPACE is...

Hey @rasheedamir thanks for looking into it. I'm trying to understand why `reloader` is eating so much memory on one of my clusters. Here is some data: Cluster | Number...

@rasheedamir I don't want to abuse this issue so I created a separate one for the memory consumption: https://github.com/stakater/Reloader/issues/977