Home/Templates/Point Argo CD at a repository
Point Argo CD at a repository
The first Application, which then manages every other application from Git.
Argo CD
Why bother
Once Argo CD is installed it does nothing until you tell it which repository to follow. The usual mistake is adding applications one at a time through the web interface, which puts the list of what should be running in the one place that is not version controlled. One Application that points at a folder of Applications fixes that on day one.
Add a folder to the repository. It appears in Argo CD without anyone running a command.
How it works
Set it up
Pick your platform, then open the level you want. Each level is complete on its own. Read the comments in the files as you go. Anything with a real consequence is explained on the line where it happens.
Argo CD. An Application pointing at a folder of Applications
What you need first
- Argo CD already installed in the cluster.
- A repository Argo CD can read, with a protected branch you are happy to have deploy itself.
What it creates
- One Application in the argocd namespace
- An AppProject fencing which repositories, namespaces, and cluster-wide kinds are allowed (Standard)
- An ApplicationSet that turns each folder under apps/ into an application (Standard)
The code
Quick startReady
repoURL: https://github.com/your-org/your-cluster-config.gitbootstrap.yaml, line 33
kubectl config current-context
Shows which cluster kubectl is pointed at. Check it first.kubectl apply -f bootstrap.yaml
Hands the Application to Argo CD.kubectl -n argocd get applications
Lists applications with their sync and health status.
Kubernetes schema passed
Last run 2026-10-02.
Open bootstrap.yaml as plain text
StandardReady
kubectl config current-context
Shows which cluster kubectl is pointed at. Check it first.kubectl apply -k .
Applies everything the kustomization lists, in order.kubectl -n argocd get applications
Lists applications with their sync and health status.
Kubernetes schema passedBuilds passed
Last run 2026-10-02.
Open applicationset.yaml as plain text
Open kustomization.yaml as plain text
Open project.yaml as plain text
HardenedReady
kubectl config current-context
Shows which cluster kubectl is pointed at. Check it first.kubectl apply -k .
Applies everything the kustomization lists, in order.kubectl -n argocd get applications
Lists applications with their sync and health status.
Builds passed
Last run 2026-10-02.
Open kustomization.yaml as plain text
Without the resources-finalizer, deleting the bootstrap Application leaves every application it created still running and managed by nobody. Both templates set it.
An AppProject narrows what an application can create. It does not make ClusterRoleBinding safe. Anything allowed to create one can bind itself to cluster-admin, and Falco needs one. The Standard project allows it, says so in a comment, and relies on the list of permitted repositories to keep strangers out.
How to undo it
kubectl delete on the Application removes it and, because of that finalizer, everything underneath it. Check that is what you meant before you press return.
What it costs
None beyond what the applications themselves use.