Skip to content

GitOps for Mere Mortals

Plain-language guides to GitOps: the practice of keeping your systems the way you want them by storing the description in git and letting automation do the rest. Written for people who run real machines — no CS degree required.

No jargon without an explanation. No "it's simple, just..." Every concept starts with the idea, then the practice.

One note on framing: GitOps is usually taught as a Kubernetes thing. It isn't only that. The core idea — desired state in git, software that converges reality to match — works for servers, configs, dotfiles, and plain scripts too. These guides keep that broader view.

Start here

  1. What GitOps Is — the core idea in plain words, and what it isn't.
  2. Core Principles — the four principles, with examples.
  3. The GitOps Loop — how a change flows from commit to running system.

Putting it to work

  1. GitOps Without Kubernetes — the broader framing: servers, configs, and scripts.
  2. Non-Kubernetes Patterns — nine concrete patterns: ansible-pull, cron scripts, etckeeper, dotfiles, compose-from-git, drift reporting, the Terraform split, PowerShell scheduled sync, and a Python converge agent.
  3. Tools Overview — what the tools do, honestly, without hype.
  4. Secrets and Safety — what doesn't go in git, and how to handle it.
  5. Common Patterns — environments, promotion, and drift detection.

Reference

  1. Troubleshooting — drift, failed syncs, and "it worked on my machine."
  2. Glossary — quick definitions, A to Z.

Writing criteria

Every guide follows the same writing criteria: plain words, no hype, honest limits, and checkable steps.