An operations model where the desired state of every cluster lives in Git, and a controller continuously reconciles reality to it.
GitOps is an operations pattern, popularized by Argo CD and Flux, where the source of truth for a system's desired state is a Git repository, and a controller running in the cluster continuously pulls from Git and reconciles the live state to match. Deploys become Git pushes; rollbacks become Git reverts; audit logs become commit history. The pattern works for Kubernetes most naturally, but the philosophy extends to any system with declarative configuration.
GitOps converts the messy 'who changed what when' question into the easily-answered 'git log'. Every change is reviewed in a PR, signed by a person, and reversible by a single Git revert. For SRE teams, that audit trail is the single biggest improvement to incident analysis since structured logs.
See the part of the platform that handles gitops in production.