Analyze Kubernetes cluster health
k8s-diagnosticsskillsetup L2★908
rohitg00/kubectl-mcp-server ↗What it does
Debug failing pods with logs, events, and dependency tracing
Best for
Root-cause analysis of pod failures faster than manual log + event review
Inputs
- · pod name, namespace, time range for logs
Outputs
- · Logs, events, node/storage status, dependency graph
Requires
- · kubectl
- · jq (optional, for log filtering)
Preconditions
Pod exists; logs available (not rotated)
Failure modes
- · logs rotated away
- · pod crashed before collection
- · node unreachable
Trust signals
- · Structured event correlation
- · Cross-resource dependency tracing