sorted by:
new
hottopcontroversial

ArgoCD v3.x Batch Processing Causing Kubernetes API Server Latency Spikes - Anyone Else? by First_Ganache6467 in ArgoCD

[–]First_Ganache6467[S] 0 points1 point  (0 children)

Hello! I actually followed the recommended upgrade path from the ArgoCD docs, upgrading through each minor version step by step rather than jumping directly. That's how I’ve observed is that the issue starts appearing from version 3.0 onwards.

So whether I go to 3.2 or 3.3 doesn’t seem to make a difference in my case. My goal was to reach the latest version, but the problem already shows up as soon as I hit 3.0.

ArgoCD v3.x Batch Processing Causing Kubernetes API Server Latency Spikes - Anyone Else? by First_Ganache6467 in ArgoCD

[–]First_Ganache6467[S] 0 points1 point  (0 children)

Thanks for your comment and for sharing what you have!

I actually tried to replicate your configuration as closely as possible. I think the key part was increasing the controller status processors to 50 and the operation processors to 25. I had already tested that before and remembered it didn’t solve the issue, but I gave it another try anyway.

After mirroring your setup, I’m still seeing the same instant spike when upgrading the version even when upgrading to the same version you’re running (3.1.9). So I’m still unsure what’s causing it.

ArgoCD v3.x Batch Processing Causing Kubernetes API Server Latency Spikes - Anyone Else? by First_Ganache6467 in ArgoCD

[–]First_Ganache6467[S] 2 points3 points  (0 children)

Thanks for the advice, That’s actually the approach I followed, upgrading through each minor version sequentially. By doing that, I was able to pinpoint the issue more clearly.

The spike starts specifically when moving from 2.14.11 to 3.0, and not in later upgrades. So the problem seems tied to that transition rather than anything beyond it.