Skip to content

Free · open source · zero to job-ready

The DevOps Engineer's Handbook

Stop collecting tutorials. Build the mental model, run the labs, break production on purpose — and walk into the interview able to explain the whole stack.

Naye ho? Yahin se shuru 👇  ·  Basics aate hain? Simulator ya Doer's Path me kudo.

Start from zero See the curriculum Enter the simulator The Doer's Path — labs that verify you

32Chapters
190Flashcards
26Real incidents
12Chaos drills
2Capstones
₹0Cost

How all of DevOps fits together

The whole handbook hangs off one mental model — two reconciliation loops that meet at the Kubernetes cluster. The outer loop builds the platform (Terraform provisions; Ansible + kubeadm configure the nodes and form the cluster) — rarely, carefully. The inner loop ships the app on every commit (App repo → CI → registry → config repo → Argo CD → rolling update). Git is the shared source of truth, CI never touches the cluster (it only writes to Git; Argo pulls), the database lives outside the cluster, and observability closes the loop back to you.

flowchart TB
  Dev(["👩‍💻 Developer"]):::dev

  subgraph INNER["🔁 INNER LOOP · ship the app · every commit"]
    direction LR
    App[("App repo")]:::store
    CI[["CI runner<br/>test · build · scan"]]:::ci
    Reg[("Registry<br/>image:sha")]:::store
    Cfg[("Config repo<br/>manifests")]:::store
    Argo["Argo CD"]:::cd
    App -->|"triggers"| CI
    CI -->|"push image"| Reg
    CI -->|"bump tag"| Cfg
    Cfg -. "watch · pull" .-> Argo
  end

  subgraph LIVE["☸️ WHERE THE LOOPS MEET"]
    direction LR
    Ing["Ingress / LB"]:::net
    K8s{{"Kubernetes<br/>rolling update · self-heal"}}:::run
    DB[("RDS<br/>state, OUTSIDE cluster")]:::store
    Ing --> K8s
    K8s -->|"read / write"| DB
  end

  subgraph OUTER["🏗️ OUTER LOOP · build the platform · rarely"]
    direction LR
    TF["Terraform<br/>VPC · EC2 · RDS"]:::infra
    Ans["Ansible + kubeadm<br/>configure · form cluster"]:::infra
    Obs["📊 Prometheus · Grafana"]:::obs
    TF -->|"provisions"| Ans
  end

  Dev -->|"git push"| App
  Users(["🌐 Users"]):::dev -->|"HTTPS"| Ing
  Argo -->|"sync"| K8s
  Reg -. "kubelet pull" .-> K8s
  Ans -->|"forms"| K8s
  TF -. "creates" .-> DB
  K8s -->|"telemetry"| Obs
  Obs -. "alerts · feedback" .-> Dev

  classDef dev fill:#e8eaf6,stroke:#3f51b5,color:#1a237e;
  classDef ci fill:#e3f2fd,stroke:#1976d2,color:#0d47a1;
  classDef store fill:#fff3e0,stroke:#ef6c00,color:#e65100;
  classDef cd fill:#f3e5f5,stroke:#8e24aa,color:#4a148c;
  classDef run fill:#e0f2f1,stroke:#00897b,color:#004d40;
  classDef infra fill:#fce4ec,stroke:#d81b60,color:#880e4f;
  classDef obs fill:#f1f8e9,stroke:#689f38,color:#33691e;
  classDef net fill:#ede7f6,stroke:#5e35b1,color:#311b92;

Two loops, one cluster. Outer = build the platform (Pets, rare). Inner = ship the app (Cattle, every commit). Git is the shared brain; CI writes to Git and Argo pulls — so CI never holds cluster credentials; the RDS state lives outside the cluster; observability feeds back to the developer.

🚀 🎬 See it move: one git push → a live podFollow the baton, step by step — the picture builds itself. (2-min interactive) ▶ Open

🇮🇳 Hinglish intuition: Do loop hain — bahar wala (Terraform/Ansible) neev + cluster banata (kabhi-kabhi), andar wala (App repo→CI→Argo) app rozana bhejta. Dono cluster pe milte hain. Git = sach ka source; CI cluster ko chhoota nahi (sirf Git likhta, Argo pull karta); database cluster ke bahar; observability wapas feedback deti. Poora course isi picture ke around hai.

Who this is for

  •   Career switchers

    Moving into DevOps / SRE / Cloud and tired of scattered tutorials? This is one structured path, start to finish.

  •   Developers

    You deploy your own code and want to stop being scared of infrastructure, pipelines, and clusters.

  •   Students & grads

    Preparing for a first role that touches CI/CD, containers, or cloud — with zero prior knowledge assumed.

  •   The "I still don't get why" crowd

    You've watched the videos but can't explain how the tools fit. This gives you the mental model, not just commands.

Why this handbook is different

  •   Systems thinking, not a tool tour

    The 2 loops · 8 bridges · 5 golden threads model is introduced early and referenced in every chapter. Tools are answers to problems, not checklist items.

  •   Built to be remembered

    Per-chapter recall gates, hidden quiz answers, ~190 flashcards, and a spaced-review schedule — padho ek baar, yaad rahe lifetime.

  •   Hands-on throughout

    Real labs, real configs, real war-stories. Command cheat-sheets you run with a terminal open. Two full capstone projects.

  •   Production-real

    A 26-scenario Incident Playbook: what actually breaks in prod, and the exact commands to fix it — symptom → diagnose → fix → prevent.

  •   Interview & job ready

    A 100+ question interview bank, X-vs-Y confusion-busters, resume bullets, a portfolio checklist, and a job-ready self-audit.

  •   Hinglish intuition 🇮🇳

    Key ideas reinforced with Hindi/Hinglish memory hooks so abstract concepts snap into place and stick.

Your learning journey

flowchart LR
  P0["🛫 Part 0<br/>Pre-flight<br/><small>terminal · git · Linux</small>"]:::p0
  P1["🧰 Part I<br/>Core toolchain<br/><small>Terraform → GitOps</small>"]:::p1
  P2["🧭 Part II<br/>Systems thinking<br/><small>the connected system</small>"]:::p2
  P3["⚙️ Part III<br/>Operate<br/><small>SRE · incidents</small>"]:::p3
  P4["🏗️ Part IV<br/>Capstones<br/><small>build it for real</small>"]:::p4
  P5["🎯 Part V<br/>Interview & career<br/><small>land the job</small>"]:::p5
  P0 --> P1 --> P2 --> P3 --> P4 --> P5
  classDef p0 fill:#e8eaf6,stroke:#3f51b5,color:#1a237e;
  classDef p1 fill:#e3f2fd,stroke:#1976d2,color:#0d47a1;
  classDef p2 fill:#f3e5f5,stroke:#8e24aa,color:#4a148c;
  classDef p3 fill:#e0f2f1,stroke:#00897b,color:#004d40;
  classDef p4 fill:#fff3e0,stroke:#ef6c00,color:#e65100;
  classDef p5 fill:#f1f8e9,stroke:#689f38,color:#33691e;

Zero prior knowledge assumed. Part 0 starts at "what is a terminal, what is YAML, what is an HTTP request."

▶ Start here

  •   New to the terminal, Git, or cloud?

    Begin at Pre-flight — it covers everything you need before touching any DevOps tool.

    00a — Pre-flight

  •   Already comfortable with the basics?

    Skim the curriculum spine to orient, then dive into Foundations.

    Curriculum index

  •   Just want to browse?

    Read The Connected System. If its mental model clicks, you'll love the rest.

    The connected system

🆓 The free, no-credit-card path

Almost everything runs locally with kind (Kubernetes-in-Docker) — no cloud account needed for Parts 0–IV. An AWS Free Tier account is only for the optional cloud capstone, and costs are negligible if you tear resources down promptly. Nobody is blocked by cost.

Curriculum at a glance

Use it in three modes (rotate all three)

Read the chapter, follow the lab, and grasp the why — not just the command. Each Part I–III chapter follows the same skeleton, so you always know where to look.

Hit the recall gate at the top of each chapter and the self-check quiz at the end (answers hidden — expand to reveal). Then run the flashcard deck on a spaced schedule.

Work the interview bank cold, use the X-vs-Y confusion-busters for the traps, and rehearse the incident playbook out loud.

Pace: ~12 weeks part-time (1–2 hrs/day) or ~6 weeks full-time — laid out week-by-week in the Study Plan. Track completions in Progress.

What you'll be able to do by the end

  •   Draw the whole stack

    Explain how code travels laptop → CI → containers → Kubernetes → production, and where observability fits.

  •   Deploy end-to-end

    Dockerfile → Helm/Kustomize → GitOps pipeline → a live, observable service with zero-downtime rollouts.

  •   Debug real incidents

    Use metrics, logs, and traces together; roll back safely; run a blameless post-mortem.

  •   Ace the interview

    Confident across Terraform, Docker, Kubernetes, CI/CD, GitOps, observability, and systems design.

→ Full job-ready checklist: 18 — Career & Job-Ready

License & provenance

Consolidated from ~20 personal study docs, lab notes, and interview-prep notes — all preserved in _source-archive/. Published in the hope it saves the next learner weeks of hunting for the right mental model.

License: CC BY 4.0 — free to use, share, and adapt with attribution. Contributions welcome — found a typo or a concept that could be clearer? Open an issue or PR. 🙏