The 12-Week Syllabus & Timeline

The program is 11 modules over 12 weeks, at roughly 30 hours per week. The order is deliberate: you learn to operate one machine by hand, then package it, orchestrate it, automate it, package it for Kubernetes, and finally observe it.

The arc

operate ─▶ containerize ─▶ orchestrate ─▶ automate ─▶ templatise ─▶ observe
 (Mod 1–5)    (Mod 6)        (Mod 7)       (Mod 8–9)  (Mod 10·Helm)  (Mod 11)

Module → week map

Module	Topic	Target weeks
1	Networking Fundamentals	Week 1
2	Linux Fundamentals	Weeks 2–3
3	Shell Scripting	Week 3
4	Git & Version Control	Week 4
5	Common Linux Services	Weeks 4–5
6	Containerization (Docker/Podman)	Weeks 6–7
7	Kubernetes & Orchestration	Weeks 8–9
8	CI/CD	Week 10
9	Infrastructure as Code	Week 11
10	Helm Charts	Week 11
11	Observability + Capstone	Week 12

(Modules 9 and 10 are both intro-depth and share Week 11 — IaC concepts plus Helm basics. Helm builds directly on Kubernetes from Module 7.)

These are targets, not a stopwatch. The early modules (1–3) are the foundation everything else stands on — it's fine if they take the time they take. There is roughly 10 hours/week of built-in slack versus a full-time load; that's your buffer for the weeks that run long.

Two things we never skip

The fundamentals (Weeks 1–3). If Linux and shell are shaky, everything later turns into copy-paste-without-understanding. Don't rush them.
The capstone (Week 12). It's where the eleven topics become one skill. It's also your headline portfolio piece.

The lab is your playground

You'll work on a real environment — a private network of Linux VMs, a live Kubernetes cluster, a container registry, databases, a Git server, and a full observability stack. The lessons point you at the exact hosts to use (for example, the Jumpbox at 10.100.100.254 is your main entry point). You're learning on real infrastructure, not toys.

Next: What's Expected After Each Module.