Overview
Direct Answer
GitOps is an operational model that treats Git repositories as the authoritative source for both infrastructure configuration and application deployment state. All desired system changes are version-controlled, reviewed, and applied through Git workflows rather than manual commands or separate deployment tools.
How It Works
A continuous reconciliation agent (typically deployed in-cluster or at infrastructure endpoints) continuously monitors a Git repository and automatically converges the live system state to match the declared configuration. When code is committed and merged, webhooks or polling mechanisms trigger automated deployment pipelines that apply infrastructure-as-code changes, with Git commit history serving as an immutable audit trail of all modifications.
Why It Matters
This approach reduces deployment risk through peer review and audit trails, accelerates incident recovery via straightforward Git rollbacks, and enforces consistency across environments. Organisations benefit from improved compliance posture, reduced human error in infrastructure management, and clearer visibility into configuration drift.
Common Applications
Kubernetes cluster management, microservices deployment pipelines, multi-environment configuration management, and disaster recovery workflows. Teams managing containerised applications, cloud-native infrastructure, and continuous delivery scenarios leverage this pattern extensively.
Key Considerations
Success requires discipline in repository structure and access control; poor Git hygiene can introduce configuration errors at scale. Managing secrets, handling non-declarative systems, and establishing appropriate branching strategies present practical challenges that organisations must address during adoption.
Cross-References(1)
More in DevOps & Infrastructure
High Availability
Site ReliabilityA system design approach that ensures a certain degree of operational continuity during a given measurement period.
Observability
ObservabilityThe ability to understand a system's internal state from its external outputs, encompassing metrics, logs, and traces.
CI/CD Pipeline
CI/CDAn automated workflow that builds, tests, and deploys software changes from development to production.
Post-Mortem Analysis
CI/CDA structured review conducted after an incident to identify root causes and prevent recurrence.
Chaos Engineering
Site ReliabilityThe discipline of experimenting on distributed systems to build confidence in their ability to withstand turbulent conditions.
Rollback
CI/CDThe process of reverting a system to a previous version or state after a failed deployment or update.
Service Level Objective
CI/CDA target value for a service level indicator that defines acceptable service performance.
Helm
Containers & OrchestrationA package manager for Kubernetes that simplifies the deployment and management of applications using charts.