Portal | Level: L2: Operations | Topics: Kubernetes Networking, Kubernetes Core | Domain: DevOps & Tooling
Symptoms: Canary Deploy Looks Healthy, Actually Routing to Wrong Backend, Ingress Misconfigured¶
| 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¶
- API Gateways & Ingress - Primer
- Chaos Engineering & Fault Injection - Primer
- Cilium & eBPF Networking - Primer
- Cross-Domain Incident Case Studies
- Grading Rubric
- Kubernetes Concept Chain - Primer
- Kubernetes Debugging Playbook - Primer
- Kubernetes Networking
- Kubernetes Networking - Primer
- Kubernetes Pod Lifecycle
- Kubernetes Pods & Scheduling - Primer
- Kubernetes Scheduler
- Kubernetes Services & Ingress - Primer
- Kubernetes Under the Covers
- Kubernetes_Core
Wiki Navigation¶
Prerequisites¶
- Kubernetes Ops (Production) (Topic Pack, L2)
Related Content¶
- Case Study: Service No Endpoints (Case Study, L1) — Kubernetes Core, Kubernetes Networking
- Kubernetes Exercises (Quest Ladder) (CLI) (Exercise Set, L1) — Kubernetes Core, Kubernetes Networking
- Skillcheck: Kubernetes Under the Covers (Assessment, L2) — Kubernetes Core, Kubernetes Networking
- Track: Kubernetes Core (Reference, L1) — Kubernetes Core, Kubernetes Networking
- API Gateways & Ingress (Topic Pack, L2) — Kubernetes Networking
- Adversarial Interview Gauntlet (30 sequences) (Scenario, L2) — Kubernetes Core
- Case Study: Alert Storm — Flapping Health Checks (Case Study, L2) — Kubernetes Core
- Case Study: CNI Broken After Restart (Case Study, L2) — Kubernetes Networking
- Case Study: CoreDNS Timeout Pod DNS (Case Study, L2) — Kubernetes Networking
- Case Study: CrashLoopBackOff No Logs (Case Study, L1) — Kubernetes Core