Who changed what 3 deploys
Every deploy ArgoCD has a record of, and the person behind it. environment person
Services in test26 1 · click one for its full history
| Service | Deploys | People | By hand | Last |
|---|---|---|---|---|
| studiosvc-infra-dev | 3 | 1 | 0 | 2026-11-14 14:30:14 UTC |
Deploys newest first
| When | Environment | App | Who | Revision | |
|---|---|---|---|---|---|
| 2026-11-14 14:30:14 UTC | test26 | studiosvc-infra-dev · infra | [email protected] | 160609b9b | |
| 2026-11-14 11:52:45 UTC | test26 | studiosvc-infra-dev · infra | [email protected] | 8c63aaf72 | |
| 2026-11-14 10:51:22 UTC | test26 | studiosvc-infra-dev · infra | [email protected] | 8c63aaf72 |
manual only marks an app whose autoSync is off — a person is the only thing that can ever deploy it, so every one of those is a deliberate hand-sync. A failed sync never becomes a history entry, so this is the record of deploys that succeeded.
Changed without ArgoCD · test26 last 7d
A kubectl edit against a live workload never touches an
Application, so it appears in no deploy above — it exists only in the cluster's audit log.
Restarts (deleting pods) are not shown: the controller recreates them from the unchanged
Deployment, so nothing declared has moved.
reading the cluster audit logs…
People in test26 1 · deploys = sync events, apps = distinct applications
| Person | Deploys | Apps | By hand | Last | |
|---|---|---|---|---|---|
| [email protected] | 3 | 1 | 0 | 2026-11-14 14:30:14 UTC | only this |