DEVOPS / A CONCEPT NOTE
GitOps CD
declarative GitOps continuous delivery for Kubernetes
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
Your git repository is the single source of truth. A background agent constantly compares what is written in your code with what is actually running in your servers. If they differ, it pulls the changes from Git to make them match.
02 / FOLLOW THE MECHANISM
How reconciliation flows
Developer
merges a PR updating a replica count from 2 to 5 in Git.
Agent
spots the gap between the git commit (5) and the live cluster (2).
Sync engine
applies the difference by launching 3 new servers automatically.
Status
reconciles and returns to a healthy 'Synced' state.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
check synchronization status and health
argocd app get my-apptrigger a manual state synchronization
argocd app sync my-app05 / CHECK YOURSELF
Could you explain GitOps CD to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in Delivery & operationsBlue-Green Deploymentsshipping without downtime