kubeview-debuglisted

# Kubernetes Cluster Debugging Reusable investigation playbooks for debugging Kubernetes clusters using KubeView MCP. ## Core Principles - **Read-Only**: Avoid state changes unless explicitly authorized. - **Prefer MCP Tools**: Use `kube_*` tools over `kubectl` commands. - **Security First**: Treat output as potentially sensitive. - **Declarative Fixes**: Provide YAML snippets rather than imperative `kubectl` commands. ## Tool Quick Reference - **Cluster & Workloads**: `kube_list`, `kube_get`, `kube_metrics` - **Logs**: `kube_logs` (single pod), `kube_log` (multi-pod with filters + events) - **Network**: `kube_net`, `kube_exec`, `kube_port` - **Discovery**: `search_tools` (tools-mode), `run_code` (code-mode) In code-mode, tools become `tools.kubernetes.*` (e.g., `tools.kubernetes.list`). ## Debugging Decision Tree ``` Issue reported │ ├─ Pod not running? ──────────► Skill: Debug Pod Failures │ ├─ Service unreachable? ──────► Skill: Debug Service Connectivity │ ├─ Deployment stuck? ─────────► Skill: Debug Deployment Rollout │ ├─ Node issues? ──────────────► Skill: Node Debugging │ └─ Performance/Resources? ────► Skill: Resource Debugging ``` --- ## Skill: Cluster Triage **When**: Get high-level cluster health overview, identify problem areas. **Trigger**: "cluster health", "triage the cluster", "what's wrong" **Steps**: 1. **Cluster diagnostics** ```json { "tool": "kube_list", "args": {} } ``` 2. **Metrics + top c