Why This Book Exists

Most Argo CD tutorials leave you with a demo: a cluster someone else provisioned, a sample guestbook app, one argocd app sync, and a green checkmark. Then you try to set it up at work and find the checkmark taught you almost nothing. You do not know why the repo-server rendered that manifest, what a sync wave actually orders, how an RBAC policy locks a teammate out of the wrong project, or what happens to your running pods when you delete an Application. The demo syncs but not your understanding.

This book takes the other route. You provision real servers, stand up a real cluster, ship a real application, and wire it to Git so that every commit reconciles onto the cluster with no one running a deploy by hand. Nothing is pre-baked, you will run every command, apply every manifest, and read every error, because the friction is the point. The steps a hosted demo hides from you are exactly the ones that teach you how Argo CD behaves when something breaks.

The book title, "GitOps the Hard Way, with Argo CD: Build Real GitOps Pipelines From Empty Clusters to Automated Deploys", was not neither an arbitrary title nor a random choice. It describes what you actually do in it.

GitOps the Hard Way, with Argo CD: