Portal | Level: L2: Operations | Topics: Alerting Rules, Kubernetes Core | Domain: DevOps & Tooling
Symptoms: Alert Storm, Caused by Flapping Health Checks, Fix Is Probe Tuning¶
| File | Purpose |
|---|---|
| symptoms.md | Problem statement and observable symptoms |
| questions.md | Diagnostic questions to work through |
| investigation.md | Full investigation path across domains |
| remediation.md | Cross-domain fix and verification |
| grading.md | Self-assessment rubric |
Cross-domain incident study — see cross-domain index for context.
Pages that link here¶
- Alerting Rules - Skill Check
- Alerting Rules Drills
- Chaos Engineering & Fault Injection - Primer
- Cross-Domain Incident Case Studies
- Grading Rubric
- Kubernetes Concept Chain - Primer
- Kubernetes Debugging Playbook - Primer
- Kubernetes Pod Lifecycle
- Kubernetes Pods & Scheduling - Primer
- Kubernetes Scheduler
- Kubernetes Under the Covers
- Kustomize - Primer
- Log Analysis & Alerting Rules (PromQL / LogQL) - Primer
- On-Call
- Ops Archaeology: The Alerts That Stopped Firing
Wiki Navigation¶
Prerequisites¶
- Kubernetes Ops (Production) (Topic Pack, L2)
Related Content¶
- Adversarial Interview Gauntlet (30 sequences) (Scenario, L2) — Kubernetes Core
- Alerting Flashcards (CLI) (flashcard_deck, L1) — Alerting Rules
- Alerting Rules (Topic Pack, L2) — Alerting Rules
- Alerting Rules Drills (Drill, L2) — Alerting Rules
- 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: DNS Looks Broken — TLS Expired, Fix Is Cert-Manager (Case Study, L2) — Kubernetes Core
- Case Study: DaemonSet Blocks Eviction (Case Study, L2) — Kubernetes Core
- Case Study: Deployment Stuck — ImagePull Auth Failure, Vault Secret Rotation (Case Study, L2) — Kubernetes Core
- Case Study: Drain Blocked by PDB (Case Study, L2) — Kubernetes Core