Real Agent Cases

Diagnose a Kubernetes pod-scheduling outage with Claude Code

Posted
by Anthropic
Last checked
Method:
How we verify

Evidence: Company case studyA write-up published by the company that makes the agent or uses it.

Outcome

Anthropic's Data Infrastructure team gave Claude Code dashboard screenshots, and it traced the problem to pod IP exhaustion and supplied the commands to add a new IP pool; Anthropic says this saved about 20 minutes during an outage.

According to Anthropic:20 minutes saved during an outage

This is the source's own number. We haven't measured it.

Agent

Claude Code

Prompt Recreated prompt

The source didn't share its exact prompt, so we wrote this from what it describes.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Help me figure out why my Kubernetes cluster stopped scheduling pods, and give me the exact commands to fix it.

Check with me first: Is this happening now, and what changed recently?

What I'll give you:
- Screenshots of the dashboards
- Access to the cloud console (I'll click through it with your directions)

Rules:
- Guide me through the console step by step to find the cause.
- Explain what each fix command does and how risky it is before I run it.
- If something is missing or unclear, ask me instead of guessing.
- Don't run anything yourself. I'll run the commands.

Output: The cause, the exact commands to fix it, and what to check afterward.

You'll know it worked when: pods start scheduling again.

Try this in:

ChatGPT Gemini Grok

Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini opens empty, so we copy the prompt for you to paste. Every button also copies it.

The source used Claude Code, which can take actions on your computer or in a browser. These are general chat tools, so results may differ, and a normal chat may only give you a plan.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.

Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Work out why my Kubernetes cluster stopped scheduling pods and give me exact commands to fix it.

Quick check first: tell me if anything below is missing or unclear.

Inputs (fill in or confirm):
- Dashboard screenshots
- Cluster provider and version
- What changed recently
- kubectl access level (read-only or admin)

Rules:
- Start with symptoms: pending pods, events, node conditions; ask me for specific outputs.
- Form 2–3 hypotheses and say what evidence would confirm each.
- Give read-only commands first; mark any command that changes state.
- Explain each fix before I run it.
- Check IP address capacity, node pool limits, quotas and taints as likely causes.
- Write down the timeline of what happened for the post-incident note.

Checkpoint: Don't run or suggest destructive commands without my explicit OK.

If you get stuck: If evidence doesn't fit, say so rather than forcing a cause. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: After the fix, check new pods schedule and IPs are available.

Output: Diagnosis, commands run, fix and follow-up actions.

Done when: pending pods schedule and I know the root cause.

Source

https://claude.com/resources/articles/how-anthropic-teams-use-claude-code

Related cases