Delivered by
Argo CD and Flux, and whether your edit survives.
Every delivered object says who delivers it, from which revision, and what happens to a change you make by hand. Two clusters of objects below, one per controller, read live from the repo's specimens on a k3d cluster with both controllers installed. Every row is a page; click through.
Argo CD
Four Applications, one project, one generator. Start at the quiet one.
project prod · kustomize @ master · auto-sync, prune, self-heal
- Repository
- https://github.com/stefanprodan/podinfo
- Revision
- dd50717, master
- Destination
- argo-podinfo, created by the sync
- Last sync
- 2026-09-05 04:25 UTC, succeeded
- If you edit it
- Argo self-heals this Application: an edit made here is put back on its next comparison, within about five minutes.
Delivers · what the last sync wrote
- Servicepodinfoargo-podinfosynced
- HorizontalPodAutoscalerpodinfoargo-podinfosynced
Belongs to
Applications in argocd · the other three, each in a different state
Flux
Two sources, five Kustomizations. Start at the one that was suspended after it had run.
./kustomize · every 10m · into flux-tenant-b · spec.suspend: true
- Flux says
- Ready · Applied revision: master@sha1:dd507173b7b75b2312a36cabe0de5f09c1ce69c8
- Rubick says
- Suspended: it is not reconciling and it is not failing
- Why the badge lies
- A suspended Kustomization keeps the Ready condition from the last time it ran, so it reads as healthy in every list, Flux's own included. It last applied dd50717; whatever has been committed since is not here.
- If you edit it
- tenant-b is suspended, so nothing is being applied and an edit here stands, until somebody resumes it, at which point it is undone.
Source
Delivers
The status words are the controllers' own. The sentences under "Rubick says" and "If you edit it" are the app's, quoted from its catalogue. The specimens live in test-manifests/k8s-gui-all.yaml with the commands that put them into these states; they need the controllers installed, so they are not part of lies.yaml.