The engineering notebook
DriftWatch - inspect Kubernetes configuration drift
Start with terminal, editor, Git, YAML, and Kubernetes object basics; then build a Go tool that compares desired repository state with observed cluster state, reports precise differences, and prepares a human-reviewed Git proposal without claiming to apply cluster changes.
Your learning trail
Verified project-agent submissions only. Reading or clicking cannot unlock progress.
Live workspace
Challenge console
$ driftwatch connect Pair your local workspace in Setup to stream validation here.
Open Setup and pair this tab to turn the console live.
Your source and command output stay local. The agent sends only bounded status logs and verified receipts.
About this path
A manual change to a running Kubernetes object can silently diverge from the configuration in Git. Without clear identity, stable comparison, and careful reporting, teams may miss meaningful drift or mistake server-generated metadata for a change that needs action.
What you will learn: Kubernetes objects, client-go, Configuration drift, Server-side dry run, Reviewed GitOps changes. Build the project through cumulative challenges with beginner explanations and local verification.
- Level
- Complete beginner to independently building and operating the project
- Format
- 16 cumulative challenges; plan 4-8 weeks at 8-12 hours per week, including practice, debugging, and a final operational exercise
- Before you start
- No prior Kubernetes, Go, YAML, or SRE experience is required. Install Go 1.24+, Python 3.11+, and Git using official instructions. Local lessons use synthetic examples and require no cluster credentials or GitHub token; optional real-cluster validation is clearly marked.