ArgoCD clusters
Every environment ArgoCD manages, side by side — what it holds, what it has been doing, and where to go next for each one.
What ArgoCD manages
reading the ArgoCD audit log…
Deploy history 343
Deploys by a person?One sync event — one app going live once. Distinct from Apps, which counts how many
DIFFERENT applications those deploys spanned.
72
of 343 recorded deploys
By the reconciler
271
autoSync doing its job
People
4
have deployed something
Unattributed?ArgoCD did not always record initiatedBy, so its oldest history entries carry no
username. They are excluded from every count on this page rather than inflating it.
0
older deploys with no name
By environment
Deploys counts sync events — one app going live once. Apps counts how many different applications those deploys spanned. Syncing 30 apps in one release is 30 deploys across 30 apps; redeploying one app 30 times is 30 deploys across 1. By hand is the share landing on apps whose autoSync is off, where a person is the only thing that can ever deploy.
| Environment | Deploys | Apps | People | By hand | Last deploy | |
|---|---|---|---|---|---|---|
| delta | 26 | 26 | 1 | 26 · 100% | 2026-11-16 05:11:58 UTC | who → |
| production | 26 | 26 | 1 | 26 · 100% | 2026-11-16 05:10:51 UTC | who → |
| automation | 17 | 14 | 3 | 17 · 100% | 2026-11-17 06:36:52 UTC | who → |
| test26 | 3 | 1 | 1 | 0 · 0% | 2026-11-14 14:30:14 UTC | who → |
| master | 0 | 0 | 0 | 0 | — | who → |
| nexus | 0 | 0 | 0 | 0 | — | who → |
| shared-neo4j | 0 | 0 | 0 | 0 | — | who → |
| test27 | 0 | 0 | 0 | 0 | — | who → |
Collected 22h ago by obs-dashboard/scripts/collect_argocd_history.py.
A sync that failed never becomes a history entry, so this counts deploys that succeeded.
Click an environment for its services, its people, and anything changed there by hand.