GitOps the Hard Way, with Argo CD (Paperback)
Aymen El Amri
Sold by Grand Eagle Retail, Bensenville, IL, U.S.A.
AbeBooks Seller since October 12, 2005
New - Soft cover
Condition: New
Ships within U.S.A.
Quantity: 1 available
Add to basketSold by Grand Eagle Retail, Bensenville, IL, U.S.A.
AbeBooks Seller since October 12, 2005
Condition: New
Quantity: 1 available
Add to basketPaperback. Most Argo CD tutorials hand you a cluster someone else built, a sample app, one argocd app sync, and a green checkmark. Then you try it at work and the checkmark turns out to have taught you nothing. You do not know why the repo-server rendered that manifest, what a sync wave orders, how an RBAC rule locks a teammate out of the wrong project, or what happens to your running pods when you delete an app.This book takes the other route. You start from empty servers and finish with an automated GitOps pipeline you built yourself. Nothing is pre-baked.The "hard way" is not difficulty for its own sake. It is doing the work yourself.What you will buildYou begin with bare servers and end with a pipeline that deploys on every Git push. Along the way you will: Provision infra with Terraform, bootstrap a cluster, and deploy an app onto it.Trace a change from a Git commit through Argo's reconciliation loop to a running resource, and learn what each component does and what breaks when it fails.Install Argo, choosing deliberately between the full, core, and custom installs, then log in from the CLI and add more clusters.Create your first Application from the CLI, then redefine the same setup as declarative manifests you keep in Git.Configure sync policy on purpose: automated sync, self-healing, pruning, retries and backoff, namespace creation, and more.Run your own code around a sync with resource hooks and sync phases, order resources with sync waves, and learn when to use hooks and when not to.Scope a teammate to exactly one project with RBAC, then verify the grant.Package your apps as a Helm chart and have Argo manage it as a versioned release.Generate many Apps from one definition with AppSets.Build a multi-branch pipeline that gives every Git branch its own live environment.And more!This book assumes you can read a Deployment, run kubectl, and open a pull request without looking it up.Every code listing (+ full-color diagram, and screenshot) lives in the companion kit. Build a real GitOps pipeline with Argo CD, from empty servers to automated deploys. Hands-on Kubernetes, raw manifests, sync policy, hooks, sync waves, RBAC, Helm, CI/CD and ApplicationSets. Companion kit with code, diagrams, screenshots. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.
Seller Inventory # 9782488111034
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.
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.
What you'll learn
By the end of this book, you will have built a full GitOps setup from nothing and operated it, not read about it. Concretely, you will be able to:
Explain what Argo CD does and does not do, and trace a change from a Git commit through the reconciliation loop to a running resource on the cluster.
Name the parts that make up Argo CD, the API server, application controller, repo-server, Redis, Dex, the ApplicationSet controller, and say what breaks when each one is unhealthy.
Provision real infrastructure from scratch: stand up servers with Terraform, bootstrap a Kubernetes cluster, and deploy an application onto it, so Argo CD has something real to manage.
Install Argo CD and choose deliberately between the full, core, and custom installs, then log in from the CLI and register additional clusters.
Create your first Application from the argocd CLI, then redefine the exact same setup as declarative manifests you keep in Git, including the repository credentials.
Read an Application manifest field by field, and configure sync policy on purpose: automated sync, self-healing, pruning and its exceptions, retries and backoff, ignoreDifferences, namespace creation, and the sync options that change how Argo CD applies resources.
Decide what happens to your running workloads when an Application is deleted, and set finalizers accordingly.
Run your own code around a sync with resource hooks and sync phases (PreSync, Sync, PostSync), and order resources within a sync using sync waves.
Create a local user and grant rights with RBAC, scoping one teammate to exactly one project, and verify the grant resolved instead of hoping it did.
Package an application as a Helm chart and have Argo CD manage it as a versioned release, passing values and tracking what is deployed.
Generate Applications from templates with ApplicationSets, producing many Applications from one definition across namespaces or clusters.
Build a multi-branch pipeline that gives every Git branch/revision its own live environment, so a push creates a deployment and a merge or delete tears it down.
And more!
You finish with a working artifact; an automated GitOps pipeline you assembled yourself, running on infrastructure you provisioned, that you can explain piece by piece.
Who it's for
Engineers who already know Kubernetes and Git and now want to run Argo CD for real: platform and DevOps engineers, SREs, security engineers, consultants standing up GitOps for clients, and anyone who inherited an Argo CD install and needs the black box to open. If you can read a Deployment and open a pull request without looking it up, you're ready.
You will install it, define and sync Applications, control sync behavior, hooks, and waves, lock down access with projects and RBAC, package with Helm, scale with ApplicationSets, and automate per-branch delivery. Each chapter ends with something running you built yourself.
The companion kitEvery code listing, full-color diagram, and screenshot lives in a companion kit you get with the book.
"About this title" may belong to another edition of this title.
We guarantee the condition of every book as it¿s described on the Abebooks web sites. If you¿ve changed
your mind about a book that you¿ve ordered, please use the Ask bookseller a question link to contact us
and we¿ll respond within 2 business days.
Books ship from California and Michigan.
Orders usually ship within 2 business days. All books within the US ship free of charge. Delivery is 4-14 business days anywhere in the United States.
Books ship from California and Michigan.
If your book order is heavy or oversized, we may contact you to let you know extra shipping is required.
| Order quantity | 6 to 16 business days | 6 to 14 business days |
|---|---|---|
| First item | US$ 0.00 | US$ 0.00 |
Delivery times are set by sellers and vary by carrier and location. Orders passing through Customs may face delays and buyers are responsible for any associated duties or fees. Sellers may contact you regarding additional charges to cover any increased costs to ship your items.