kubeview-debug

Triage Kubernetes cluster health and workload failures using KubeView MCP tools.

5|2|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/mikhae1/kubeview-mcp --skill kubeview-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubeview-debug
Source: https://github.com/mikhae1/kubeview-mcp/tree/main
Command: npx skills add https://github.com/mikhae1/kubeview-mcp --skill kubeview-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides structured playbooks to triage Kubernetes clusters step-by-step with KubeView MCP whenever pods crash, rollouts stall, services lose endpoints, nodes report pressure, or resource bottlenecks emerge, all without any write access.

Core Features & Use Cases

  • Cluster Triage: Start with kube_list plus kube_metrics to capture overall health, surface namespaces with CrashLoopBackOff or Pending workloads, and highlight high-resource consumers.
  • Specialized Investigations: Follow the decision tree to invoke kube_get, kube_logs, kube_log, kube_net, kube_exec, or kube_port for focused diagnostics (pods, deployments, services, nodes, resource usage).
  • Advanced tooling: When more logic is needed, leverage plan_step for multi-step coordination or run_code in code-mode to bulk analyze CRDs like pods missing limits while preserving sensitive data.

Quick Start

Use the kubeview-debug skill to triage cluster health by running kube_list diagnostics, gathering kube_metrics summaries, and drilling into kube_get/kube_logs calls for the affected namespaces.

Frequently Asked Questions about kubeview-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Kubernetes pods stuck in CrashLoopBackOff without full cluster write access?

Debug Kubernetes CrashLoopBackOff pods by orchestrating KubeView MCP tools like kube_list and kube_logs to triage failures without requiring write access. The skill captures cluster health and drills into affected namespaces to identify crash causes.

What is the best way to diagnose Kubernetes services losing endpoints during rollout stalls?

Diagnose Kubernetes service endpoint loss by following a structured decision tree using kube_get and kube_net tools to inspect service connectivity. This replaces manual CLI triage and systematically isolates network or selector configuration issues.

How do I monitor Kubernetes node pressure and resource throttling affecting workloads?

Monitor Kubernetes node pressure and resource throttling by running kube_metrics to capture overall cluster health and surface high-resource consumers. The skill highlights nodes reporting pressure and identifies workloads suffering from resource bottlenecks.

Can I run code to bulk analyze Kubernetes CRDs like pods missing resource limits?

You can bulk analyze Kubernetes CRDs and pods missing limits by leveraging run_code in code-mode within the skill. This allows custom logic execution to filter and inspect resource configurations while preserving sensitive data.

Does this Kubernetes debugging approach require installing kubectl or direct cluster credentials?

This Kubernetes debugging approach uses KubeView MCP tools instead of requiring direct kubectl CLI installation or manual credential management. It orchestrates kube_list, kube_get, and kube_metrics calls with explicit JSON arguments per diagnostic stage.

What are the limitations of using read-only KubeView MCP tools for cluster triage?

A limitation of using read-only KubeView MCP tools for cluster triage is the lack of write access, meaning you cannot directly patch resources or restart deployments. The skill focuses strictly on diagnostics, leaving remediation to separate processes.