It's 3 a.m. and a pod is stuck in OOMKilled . You know the fix: raise the memory limit and restart. You've done it a dozen times. So why is a human still doing it?

I built a small project to see how far an AI agent could take that on-call chore. It receives Prometheus alerts, investigates the live cluster, fixes what's safe to fix, and hands the rest to a human with a JIRA ticket and a Slack message.

The code is on GitHub: bedrock-agentcore-eks-monitor .

The idea

Most Kubernetes failures fall into two buckets:

Mechanical: the fix is well known and low risk (OOMKilled, a transient CrashLoopBackOff).

Needs a human: the fix needs judgment or access the agent shouldn't have (a bad image tag, a missing secret, a node that is down).

An agent is useful in both. For the first bucket it acts.…