GitOps

GitOps Principles

The four principles that define GitOps.

25 min read beginner 3 objectives

Status

Not started

What you will learn

  • State four GitOps principles
  • Contrast push and pull
  • Understand the benefits

New to this? Start here

The basics, in plain English

GitOps is a way of running infrastructure where Git, the place you store code, becomes the single source of truth for how everything should look. You describe the desired state in files, and an automatic tool makes the real system match those files. To change something, you change the files, not the live system.

GitOps
Managing your systems by editing files in Git and letting a tool apply them.
Source of truth
The one authoritative place that defines how things should be, here it is Git.
Desired state
A written description of how your system should look.
Reconciliation
A tool constantly comparing reality to the files and fixing differences.
Declarative
Saying what you want, not the step-by-step of how to get there.
Pull request
A proposed file change others review before it goes live.
01

Declarative & reconciled

The desired state is declarative, versioned in git, pulled automatically, and continuously reconciled. Git becomes the single source of truth and audit log.

Finished this topic?

Mark it done to earn 100 XP and keep your streak alive.