k8s-debugger

Run kubectl queries via Friday MCP to diagnose Kubernetes pod failures.

31|4|Updated Aug 24, 2021
One-click install
npx skills add https://github.com/razorpay/trino-gateway --skill k8s-debugger
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: k8s-debugger
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/k8s-debugger
Command: npx skills add https://github.com/razorpay/trino-gateway --skill k8s-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

Comprehensive Kubernetes pod debugging and log analysis using the Friday MCP server. Use the MCP tools to execute kubectl commands and inspect pods, deployments, namespaces, and logs โ€” then synthesize findings into a root cause and recommended fix.

Core Features & Use Cases

  • Pod status and lifecycle checks (phase, restart count, events) to quickly identify issues.
  • Log analysis (current and previous container logs) to surface failures.
  • Check resource usage and limits (CPU/memory) to detect throttling or OOM conditions.
  • Synthesize root-cause findings and provide remediation recommendations.
  • Friday MCP integration for read-only, auditable command execution of kubectl queries.

Quick Start

Check the pod status in your target namespace, then fetch recent logs and events to identify the root cause using the Friday MCP execute tool.

Frequently Asked Questions about k8s-debugger

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

FAQPage Schema
How do I debug a Kubernetes pod stuck in CrashLoopBackOff?โ–ผ

To debug a Kubernetes pod in CrashLoopBackOff, check the pod status and lifecycle events, then fetch current and previous container logs to surface the failure. This Skill aggregates status, logs, and events to produce a structured root-cause report.

How do I find the root cause of Kubernetes pod startup failures?โ–ผ

Finding the root cause of Kubernetes pod startup failures involves inspecting pod phases, restart counts, and recent events. This Skill executes read-only kubectl queries via Friday MCP to aggregate logs and events, synthesizing findings into remediation recommendations.

Can I check Kubernetes resource limits and CPU throttling using kubectl?โ–ผ

Yes, you can check Kubernetes resource limits and CPU throttling using kubectl queries. This Skill inspects CPU and memory usage against configured limits to detect throttling or OOM conditions, then includes these findings in the root-cause report.

Does this Kubernetes debugging approach work across different namespaces and clusters?โ–ผ

Yes, this Kubernetes debugging approach works across different namespaces and clusters. It supports namespace health checks and applies to investigating performance issues across your cluster infrastructure using read-only, auditable kubectl command execution.

What is the best way to analyze previous container logs in Kubernetes?โ–ผ

The best way to analyze previous container logs in Kubernetes is to fetch them alongside current logs and pod events. This Skill uses Friday MCP to execute kubectl queries, aggregating these outputs to identify the root cause and recommend a fix.