Does the backup actually come back?
Operational scar tissue turned into tools: the untested restore, the lost evidence, the diagram that no longer matches the cluster.
Before the incident
Most of these exist because something went wrong once and the tooling to understand it did not exist at the time. Anything not publicly released is marked.
Before
Prove the assumptions while it is cheap. A restore that has never run is a hypothesis, and a diagram nobody checks is fiction.
The papers
Every paper carries the methodology behind any number it emits, and what the tool deliberately does not do. Pick them up from the catalogue.
- Answering the operational questions engineers get wrong under pressureclient-side browser tools for platform engineers
- Keeping the architecture diagram true to what is deployeda C4 container diagram generated from Terraform state and a live cluster
- Proving the backup restores, nightly, with nobody watchinga scheduled restore-and-smoke-test harness
- Finding the configuration difference between two environments, safelyan environment-variable differ with secret masking on by default
- The scheduled job that silently skips when the clocks changea cron translator with timezone-aware next runs and DST warnings
The questions in between, in your browser
Cache headers, CronJob schedules, probe timings, regex backtracking, NetworkPolicy reachability: one input, one clear answer, shareable by URL. No accounts, no backend, no telemetry.
A question about any of this?
Ask about any tool or paper on this page in one message, and get one reply. The tools are open source and the papers are free.