Install the ApplicationSet controller (bundled with Argo CD v2.3+; verify with `kubectl get deploy -n argocd argocd-applicationset-controller`)
Author an ApplicationSet manifest using the `git` generator with `directories` pointing to a path glob in your config repo (e.g., `apps/*`)
Define the Application template inside the ApplicationSet spec; use `{{path.basename}}` to parameterize the Application name and target namespace per discovered directory
Add the ApplicationSet to the cluster with `kubectl apply -f applicationset.yaml`; Argo CD creates one Application per matched directory
Push a new directory to the config repo to automatically provision a new Application; remove the directory to trigger deletion (if configured)
Use `argocd appset list` and `argocd appset get <name>` to inspect generator output and debug template rendering
Known gotchas
The generator rescans on a polling interval (default 3 min); force a refresh with `argocd appset refresh <name>` or by annotating the ApplicationSet
Template errors in the ApplicationSet do not surface clearly — check the applicationset-controller logs with `kubectl logs -n argocd deploy/argocd-applicationset-controller`
With `syncPolicy.preserveResourcesOnDeletion: false`, deleting an ApplicationSet deletes all generated Applications and their resources; set to true in production
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp