Portal | Level: L2: Operations | Topics: Kubernetes Core, Linux Networking Tools | Domain: DevOps & Tooling
Ops Archaeology: The DR That Looks Ready But Isn't¶
| File | Purpose |
|---|---|
| briefing.md | Scenario briefing with artifacts |
| hints.md | Progressive hints (timed) |
| answer_key.md | Full solution and skills tested |
Ops Archaeology exercise — see ops-archaeology index for context.
Pages that link here¶
- Answer Key: The DR That Looks Ready But Isn't
- Mental Models (Core Concepts)
- Ops Archaeology: Reverse-Engineering Production Systems
- Ops Archaeology: The Cluster That Disagrees With Itself
- Pattern: Untested Rollback Procedure
- Symptoms
- Symptoms: API Latency Spike, BGP Route Leak, Fix Is Network ACL
Wiki Navigation¶
Prerequisites¶
- Kubernetes Ops (Production) (Topic Pack, L2)
Related Content¶
- Mental Models (Core Concepts) (Topic Pack, L0) — Kubernetes Core, Linux Networking Tools
- Ops Archaeology: The Cluster That Disagrees With Itself (Case Study, L2) — Kubernetes Core, Linux Networking Tools
- Adversarial Interview Gauntlet (30 sequences) (Scenario, L2) — Kubernetes Core
- Case Study: API Latency Spike — BGP Route Leak, Fix Is Network ACL (Case Study, L2) — Linux Networking Tools
- Case Study: ARP Flux Duplicate IP (Case Study, L2) — Linux Networking Tools
- Case Study: Alert Storm — Flapping Health Checks (Case Study, L2) — Kubernetes Core
- Case Study: Canary Deploy Routing to Wrong Backend — Ingress Misconfigured (Case Study, L2) — Kubernetes Core
- Case Study: CrashLoopBackOff No Logs (Case Study, L1) — Kubernetes Core
- Case Study: DHCP Relay Broken (Case Study, L1) — Linux Networking Tools
- Case Study: DNS Looks Broken — TLS Expired, Fix Is Cert-Manager (Case Study, L2) — Kubernetes Core