Kubernetes AI SRE Agent Finds a Crash Loop Nobody Asked About: AURA

You ask for a routine health check and expect a clean baseline. What came back was a pod that had restarted 788 times, unrelated to the question.

Learn more about AURA → https://www.mezmo.com/aura
Get started today → https://github.com/mezmo/aura
Get deployment help → https://www.mezmo.com/contact

AURA is connected to a Kubernetes cluster and to Prometheus through read-only MCP servers, running as one coordinator with two specialized workers. The prompt is one sentence: check the health of the cluster, and confirm whether all the pods are running.

What comes back is not a baseline. AURA names the state as CrashLoopBackOff and attaches the restart count to it.

Partway through, some of the metrics work hits a provider rate limit. Rather than filling the gap, AURA states that the analysis is incomplete. The whole run is inspectable end to end: the plan, the workers assigned to it, and every tool call made.

A second question, about a suspected memory issue, runs two workers and 16 tool calls and returns nothing. The pods are running, ready, and at zero restarts, and the metrics do not support the theory, so AURA says so rather than producing a cause to match the question.

AURA reads and reports here. Both MCP servers are read-only and the run ends with findings and evidence rather than an applied change.

For more detail, visit
https://www.mezmo.com/videos/kubernetes-ai-sre-agent-finds-an-unnoticed-crash-loop

Chapters

0:00 The question, and the setup

0:18 A routine health check turns up a crash loop

0:35 Reporting an incomplete analysis instead of guessing

0:50 A second question, and a finding that is not there

1:09 From an unexamined cluster to a specific issue

#AISREAgent #Kubernetes #Prometheus