argocd webhook refresh jitter configuration

Introduced 2026-08-04 · score 0.99

HOW TO USE IT

When a webhook affects many applications and refresh bursts strain repo-server, configure webhook jitter in `argocd-cm` to spread refreshes over time. Optionally raise the refresh worker count in `argocd-cmd-params-cm` to drain the queue faster after delays expire.

apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-cm
data:
  webhook.refresh.jitter: "60s"
  webhook.refresh.jitter.threshold: "10"

apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-cmd-params-cm
data:
  server.webhook.refresh.workers: "40"

WHY THIS HELPS

Reduce repo-server load when a webhook affects many applications.

BEFORE THIS CHANGE

Webhook processing enqueued all affected applications at the same instant, causing bursts of repo-server calls and cache stampedes.

REQUIREMENTS AND LIMITATIONS

Version: v3.5.0
webhook.refresh.jitter (required): Maximum random delay before each webhook-triggered application refresh; `0` disables jitter and is the default. Example: `60s` means a delay from 0 to 60 seconds.
webhook.refresh.jitter.threshold: Minimum affected application count before jitter applies; jitter applies only when the event affects more than the threshold. Default: `10`.
server.webhook.refresh.workers: Concurrent workers processing webhook-triggered application refresh requests. Default: `20`.
--webhook-refresh-workers: `argocd-server` flag for the number of webhook refresh requests processed concurrently; default: `20`.
Jitter is disabled when `webhook.refresh.jitter` is `0` (default).
The default `webhook.refresh.jitter.threshold` is `10`; jitter applies only when more than that many applications are affected.
`server.webhook.refresh.workers` defaults to `20`.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

argocd webhook refresh jitter configuration