What is k8s-troubleshoot?

A step-by-step guide for finding and diagnosing problems in Kubernetes, a system for running containerised applications across computers. It uses infrastructure tools to inspect pods, logs, services, metrics and deployments.

Use it to investigate pods that will not start, trace high application latency, find memory leaks and check resource usage, deployments, dependencies and node capacity.

It gives the agent a consistent way to investigate failed starts, slow requests and memory problems instead of guessing from symptoms.

k8s-troubleshoot — Skill for Claude Code and Codex by batu-sonmez

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add batu-sonmez/infraclaude --skill k8s-troubleshoot

Clone the repo

git clone --depth 1 https://github.com/batu-sonmez/infraclaude

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/k8s-troubleshoot/github.svg)](https://agentmods.dev/skills/batu-sonmez/infraclaude/k8s-troubleshoot)

Your own site

<a href="https://agentmods.dev/skills/batu-sonmez/infraclaude/k8s-troubleshoot"><img src="https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/k8s-troubleshoot/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/batu-sonmez/infraclaude/k8s-troubleshoot"><img src="https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/k8s-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 655 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00655
Opus 5.5	$0.00000	$0.00262
Sonnet 5.5	$0.00000	$0.00131
Haiku 4.5	$0.00000	$0.00065

Measured 2mo ago against content hash 314d31262cab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

k8s-troubleshoot scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/k8s-troubleshoot/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kubernetes Troubleshooting Guide

When debugging Kubernetes issues, follow this systematic approach using InfraClaude tools.

Pod Not Starting

Use k8s_get_pods to identify the pod status
Use k8s_describe_pod to check the Events section
Common causes:
- ImagePullBackOff: Wrong image name/tag, private registry auth, rate limiting
- CrashLoopBackOff: Application error — check logs with k8s_get_pod_logs (also try previous: true)
- Pending: Insufficient resources — check k8s_top_nodes for node capacity
- Init container failing: Check init container logs specifically with container parameter
- CreateContainerConfigError: Missing ConfigMap/Secret references

High Latency Investigation

Use prom_instant_query with: rate(http_request_duration_seconds_sum[5m]) / rate(http_request_duration_seconds_count[5m])
Check upstream dependencies with k8s_get_services and endpoint health
Look for resource saturation: k8s_top_pods — pods at CPU limit will be throttled
Check for recent deployments: k8s_rollout_status
Check for noisy neighbors on the same node: k8s_top_nodes

Memory Leak Detection

Use prom_range_query for container_memory_working_set_bytes over 24h
Look for monotonically increasing memory without plateaus
Check OOMKilled events: k8s_get_events with type=Warning
Check container restart counts with k8s_get_pods
Compare requested vs actual memory in k8s_describe_pod

Deployment Rollout Issues

Use k8s_rollout_status to check progress
Common issues:
- ProgressDeadlineExceeded: New pods failing to start — check pod events
- Insufficient replicas: Check resource quotas and node capacity
- Readiness probe failing: Application not healthy — check logs and probe config
Use k8s_rollback_deployment if the new version is broken

Node Issues

Use k8s_get_nodes to check node status
Use k8s_describe_node to check conditions:
- MemoryPressure: Node running out of memory
- DiskPressure: Node disk is full
- PIDPressure: Too many processes
Use k8s_top_nodes to see actual resource usage
If a node is problematic, use k8s_cordon_node to prevent new scheduling

Read the full file on GitHub · 58 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 58 lines · 0 tokens per session scan A 314d31262cab

Subscribe to this mod's changes

k8s-troubleshoot is a skill published in the GitHub repository batu-sonmez/infraclaude (0 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 655 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Containers Debugging DevOps and cloud

k8s-troubleshoot next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
k8s-troubleshootbatu-sonmez/infraclaude	Skill	0	8mo ago	MIT	A	0	Claude Code, Codex
hermes-s6-container-supervisionNousResearch/hermes-agent	Skill	262k	today	MIT	A	20	Claude Code, Codex
smoke-testgarrytan/gbrain	Skill	32k	today	MIT	A	79	Claude Code
aks-troubleshootingmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	221	Claude Code
competition-container-runtimezhaoxuya520/reverse-skill	Skill	44k	1mo ago	MIT	A	109	Codex
meta-home-it-rescueopensquilla/opensquilla	Skill	7.1k	yesterday	Apache-2.0	A	65	Claude Code, Codex
aks-gpu-inferencemicrosoft/skills	Skill	3.2k	yesterday	MIT	A	114	Claude Code