29 lines
1.5 KiB
Markdown
29 lines
1.5 KiB
Markdown
---
|
|
title: "GitOps"
|
|
type: concept
|
|
tags: [devops, gitops, infrastructure, git]
|
|
sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]
|
|
last_updated: 2026-04-22
|
|
---
|
|
|
|
## Summary
|
|
GitOps is a DevOps methodology that uses Git as the single source of truth for managing infrastructure and application deployments. All desired state is stored in Git repositories, and automated tools (like ArgoCD or Flux) continuously reconcile the actual cluster state with the desired state defined in Git. It is identified as a key future trend in DevOps for managing both infrastructure and deployments declaratively.
|
|
|
|
## Key Concepts
|
|
|
|
### Core Principles
|
|
1. **The entire system described declaratively** — All infrastructure and application configurations are stored as code
|
|
2. **The canonical desired state in Git** — Git is the source of truth; any change goes through Git workflow
|
|
3. **Approved changes automatically pulled into the system** — Automated agents detect drift and reconcile
|
|
|
|
### Tools
|
|
- **ArgoCD** — Kubernetes-native GitOps controller
|
|
- **Flux** — GitOps toolkit for Kubernetes
|
|
- **Atlantis** — Terraform GitOps automation (mentioned in CTP topics)
|
|
|
|
## Connections
|
|
- [[DevOps Culture]] — GitOps is an operational pattern emerging from DevOps culture
|
|
- [[Infrastructure as Code (IaC)]] — GitOps extends IaC with Git-centric workflows
|
|
- [[CI/CD Pipeline]] — GitOps can be considered a specialized CI/CD pattern
|
|
- [[Continuous Improvement (Kaizen)]] — GitOps enables continuous, auditable improvements
|