--- name: k8s-troubleshooting description: Use when investigating Kubernetes issues with boxctl - provides graph-based traversal with namespace scoping and event correlation --- # K8s Troubleshooting Graph-based investigation of Kubernetes issues using boxctl's 93 k8s monitoring scripts. ## When to Use User invokes `\/k8s` after discovery has identified relevant scripts. ## Key Difference from Baremetal Baremetal = vertical (OS stack). K8s = horizontal (resource graph). ``` Pod → Deployment → Service → Ingress ↓ ↓ ↓ Events ReplicaSet Endpoints ``` Traverse the graph based on symptoms. ## Investigation Pattern ```dot digraph k8s_investigation { "Scope namespace" -> "Check events first"; "Check events first" -> "Identify affected resource"; "Identify affected resource" -> "Check resource health"; "Check resource health" -> "Issue found?" [label=""]; "Issue found?" -> "Traverse to related" [label="no"]; "Issue found?" -> "Report conclusion" [label="yes"]; "Traverse to related" -> "Check resource health"; } ``` ## Step Tracking ``` ## Investigation: in namespace **Step N\/10**: Checking **Graph position**: → **Finding**: **Next**: ``` ## Running Scripts ```bash # Always specify namespace boxctl run