GitOps
GitOps is an operating model in which a system desired state is declared in Git and an automated process continuously reconciles the running system to it.
What is gitops?
GitOps is an operating model in which a system desired state is declared in Git and an automated process continuously reconciles the running system to it.
Plain and technical
The repository becomes the single description of what should be running. Software watches it and makes reality match, so deploying is a matter of merging a change rather than running a command.
GitOps depends on a reconciliation loop that continuously compares declared state against actual state, which gives it two properties plain deployment automation lacks: drift is detected because comparison is continuous, and rollback is a revert of the declaration. Progressive delivery and metric-gated promotion are usually layered on top, since plain reconciliation does not evaluate release health.
What it looks like in practice
Nearby vocabulary
Continuous delivery
Continuous delivery is the practice of keeping software in a state where any change that has passed verification could be released to production at any time.
Configuration drift
Configuration drift is the divergence between the state a system was declared to have and the state it actually has, caused by out-of-band changes.
Infrastructure as code
Infrastructure as code is the practice of defining infrastructure in versioned, machine-readable files rather than configuring it by hand.
Kubernetes
Kubernetes is an open-source system that runs containerised applications across a group of machines, keeping the running state matched to a declared one.
How DevOpsArk handles gitops
More definitions
See these concepts in a running system
A 30-minute walkthrough against your own infrastructure rather than a slide about the theory.