All 28 GitOps Principles questions
More in GitOps Principles
What belongs in Git and what should not in a GitOps setup? How are secrets managed securely in a GitOps workflow? How does GitOps improve security and compliance? How does GitOps enable auditability and compliance evidence? How do you handle non-Kubernetes resources in a GitOps model? How does GitOps improve developer experience? What role do webhooks play in GitOps with ArgoCD? How do you structure Git repositories for GitOps at scale? What is the reconciliation loop and how often does ArgoCD run it? How does GitOps support disaster recovery?
Advertisement
Back to results for “Applications”
ArgoCD › GitOps Principles

What is the difference between GitOps and Infrastructure as Code (IaC)?

Intermediate

Answer

IaC is codifying infrastructure declaratively; GitOps is an operating model that uses IaC plus Git as the source of truth and an agent that continuously reconciles. All GitOps uses IaC, but not all IaC is GitOps—IaC run manually via a pipeline isn't GitOps without pull-based continuous reconciliation.
Real-world example Terraform applied by hand is IaC; the same declarations reconciled continuously by an in-cluster agent is GitOps.

Common follow-ups: Is all IaC GitOps? | What does GitOps add to IaC?

Applications Multi-cluster GitOps Principles
All 28 GitOps Principles questions