Portal | Level: L2: Operations | Topics: DNS, TLS & PKI, Kubernetes Core | Domain: DevOps & Tooling
Symptoms: DNS Looks Broken, TLS Is Expired, Fix Is in Cert-Manager¶
| 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¶
- BMC Clock Skew - Certificate Failure
- Chaos Engineering & Fault Injection - Primer
- Cross-Domain Incident Case Studies
- DHCP & IP Address Management - Primer
- DNS Deep Dive - Primer
- DNS Operations - Primer
- DNS Resolution Taking 5+ Seconds Intermittently
- DNS Split-Horizon Confusion
- Grading Rubric
- HTTP Protocol - Primer
- Kubernetes Concept Chain - Primer
- Kubernetes Debugging Playbook - Primer
- Kubernetes Pod Lifecycle
- Kubernetes Pods & Scheduling - Primer
- Kubernetes Scheduler
Wiki Navigation¶
Prerequisites¶
- Kubernetes Ops (Production) (Topic Pack, L2)
Related Content¶
- Case Study: Deployment Stuck — ImagePull Auth Failure, Vault Secret Rotation (Case Study, L2) — Kubernetes Core, TLS & PKI
- Case Study: User Auth Failing — OIDC Cert Expired, Cloud KMS Rotation (Case Study, L2) — Kubernetes Core, TLS & PKI
- Networking Deep Dive (Topic Pack, L1) — DNS, TLS & PKI
- Scenario: DNS Looks Fine but App Fails (Scenario, L2) — DNS, TLS & PKI
- AWS Route 53 (Topic Pack, L2) — DNS
- Adversarial Interview Gauntlet (30 sequences) (Scenario, L2) — Kubernetes Core
- Case Study: Alert Storm — Flapping Health Checks (Case Study, L2) — Kubernetes Core
- Case Study: BMC Clock Skew Cert Failure (Case Study, L2) — TLS & PKI
- Case Study: Canary Deploy Routing to Wrong Backend — Ingress Misconfigured (Case Study, L2) — Kubernetes Core
- Case Study: CoreDNS Timeout Pod DNS (Case Study, L2) — DNS