GitOps
ExplainedConcept
Way of working where the desired state of infrastructure and deployments lives in Git.
GitOps, explained
Written by EduVerseWhat it is
GitOps is a way of running deployments where a Git repository describes exactly what should be running, for example which version of each service, with which settings. A tool inside the cluster, such as Argo CD or Flux, keeps comparing the cluster with that repository and changes the cluster until they match.
Why teams use it
With manual deploys, nobody quite knows what’s running or who changed it. In GitOps every change is a commit, so you get review through pull requests, a full history and an easy rollback: revert the commit. It also means people and pipelines don’t need direct write access to production.
An example from work
To release a new version you don’t run a deploy command; you open a pull request that changes the image tag in values.yaml for the payments service. After the merge, Argo CD briefly shows the app as OutOfSync, syncs it, and the new pods start. A manual kubectl edit on the cluster shows up as drift too.
Our own explanation, not a quote from the book.
In the book
Sentences from The Software Realm, Decoded that mention GitOps, exactly as printed.
3 more passages about GitOps in the full book
Read every conversation where GitOps comes up, with the interactive slides and demos.
Where it fits
Declarative management of Kubernetes deployments through Git
Coverage in the book
Explained and compared with alternatives, so you know where and why it’s used.
