GitOps uses Git as the single source of truth for both application code and infrastructure configuration. Changes are made through pull requests, reviewed by teammates, and automatically applied to the cluster. No manual kubectl commands or console clicking.

How GitOps Works

In GitOps, your Kubernetes manifests live in a Git repo. Tools like ArgoCD or Flux watch the repo and automatically sync the cluster to match. Want to scale up? Change the replica count in a YAML file, open a PR, merge, and ArgoCD applies the change.

Key Concepts

  • Declarative State — The desired state of your infrastructure is declared in Git — the system converges to match
  • Reconciliation Loop — GitOps controllers continuously compare Git state to actual state and fix any drift

GitOps Educators

Frequently Asked Questions

Is GitOps only for Kubernetes?

GitOps originated in the Kubernetes ecosystem, but the principle (Git as source of truth, automated reconciliation) applies to any infrastructure. Terraform with CI/CD pipelines follows similar patterns.

Want a structured learning path?

Plan a GitOps Lesson →