Mykola Pelekh

> We are encountering a similar issue. In large clusters where Argo CD monitors numerous resources, it is significantly slow in processing watches—taking approximately 7 minutes in our case. Consequently,...

Hi @andrii-korotkov-verkada. Thanks for replying Do you mean the following fixes? - https://github.com/argoproj/gitops-engine/commit/6b2984ebc47085852a7b63a0fd0b73c52e986217 - https://github.com/argoproj/argo-cd/commit/267f243a899483fea0a4e6a613c18f62bd342c7e Thanks for your contribution. IterateHierarchyV2 looks promising. I actually patched v2.10.9 with the above commits....

@crenshaw-dev No, we don't set CPU limits at all and still have plenty of resources on the node. We found that the potential reason is lock contention. Here, I added...

> Hey, Daniel! In our setup each container (aka pod) has tunl interface in its namespace. So we terminate ipip there @tehnerd We have a similar setup, by the way...

> We have custom patch and it works just fine for us. I just need to find time to do proper upstreaming... Honestly with amount of other work it is...

> https://gist.github.com/tehnerd/f217e4ebf75d08f8d6dc3ffee4392ae4 on top of 1.15 version Thank you @tehnerd. I will give it a try.

> https://gist.github.com/tehnerd/f217e4ebf75d08f8d6dc3ffee4392ae4 on top of 1.15 version @tehnerd I verified the patch you shared, and it works as expected. With it, all the lookups and firewall rules are done for...

@ziyi-xie Please, take a look.

**The issue** In large clusters where Argo CD monitors numerous resources, the processing of watches becomes significantly slow—in our case (total k8s resources in cluster: ~400k, Pods: ~76k, ReplicaSets: ~52k),...

> @mpelekh would you be interested in joining a SIG Scalability meeting to talk through the changes? @crenshaw-dev Yes, I’d be happy to join the SIG Scalability meeting to discuss...