TL;DR

GitOps with Argo CD means one thing: the desired state of your cluster lives in Git, and Argo CD continuously works to make the cluster match it. If it is not in Git, it is not deployed for long.

Install takes minutes: create a namespace, apply the official install manifest, and expose the UI via port-forward for learning — do not skip proper ingress and SSO when you move beyond a test cluster.

An Application is just a pointer: source repo + path + destination cluster/namespace. Get that one YAML right and most of Argo CD clicks into place.

Turn on automated sync carefully: prune and selfHeal are powerful, and they will faithfully delete or revert things you did not mean them to. Start manual, automate once the repo is trustworthy.

Rollback in GitOps is a Git revert, not an emergency kubectl edit.…