GitOps with Argo CD
Reconcile a cluster declaratively from a Git repo.
0 of 6 steps
What you will end up with
A git-driven deployment flow
Auto-sync and self-heal
Full audit trail in git
Build steps
0/6Create the argocd namespace, then apply Argo CD’s install manifest into it. You are installing the robot that will watch your Git repo on your behalf.
Push your Kubernetes YAML files into a dedicated Git repo, separate from your app’s source code. This repo becomes the single source of truth for what should be running.
Write an Application manifest pointing at your config repo’s path and the target cluster, then apply it. It is the leash connecting Argo CD to that one specific repo folder.
Set syncPolicy.automated with selfHeal: true in the Application spec. Now if someone manually edits the cluster, Argo CD quietly reverts it back to match Git.
Edit a YAML file in the config repo, open a pull request, and merge it to main. This should be the only front door you ever use to change the cluster.
Open the Argo CD UI and watch the app flip from OutOfSync to Synced within seconds of your merge. That flip is the robot noticing new instructions and following them.
Before you start