Argo CD vs Flux: equivalent API examples

Documentation reviewed 2026-11-10 against Argo CD 3.6.1 and Flux 2.10.0.
These files illustrate documented APIs. They have not been deployed as an
independent cluster benchmark. Use a disposable test cluster.

1. Follow the selected project release's official installation guide:
   https://argo-cd.readthedocs.io/en/stable/getting_started/
   https://fluxcd.io/flux/get-started/
2. Use one controller stack per test cluster. Do not let both own the same app.
3. Create namespace guestbook. Tool namespaces argocd / flux-system must exist.
4. Apply argo-guestbook.yaml OR the two flux-guestbook*.yaml files.
5. Inspect source revision, conditions, workload health and events.

Both use the same public upstream repository, branch, path and destination:
https://github.com/argoproj/argocd-example-apps.git
master / kustomize-guestbook / namespace guestbook

The branch moves. Record the reviewed revision and check the sample workload's
image availability and architecture support before testing. Pin revisions and
images for repeatability. No repository credentials are needed for this source.

Pruning is explicitly enabled. Only remove tracked sample resources when
cleaning up; follow the tool's documented deletion/finalizer behavior.
The Argo default project and Flux installer permissions are tutorial defaults,
not a production tenant policy. Restrict project and service account authority
before sharing a real cluster. Never include secrets in these files.