MetalBear
Read post

Auto-Verifying Your AI-SRE’s Fixes Against Your Real Cluster

When an AI-SRE proposes a fix for a production incident, verifying it against real cluster state is the hard part — unit tests and mocks can't reach the bugs that matter. This guide shows how to wire `mirrord exec` into an AI-SRE's post-suggestion hook so every candidate patch is automatically tested against the live cluster before a human reviews it. Using mirrord's steal mode with a header filter, the patched service runs locally but connects to real in-cluster downstreams, inheriting the target pod's network identity, secrets, and environment. The verification loop runs a repro script or load test twice (patched vs. unpatched), diffs the metrics, and either approves or rejects the fix — all in seconds, without a deploy. The post also covers why this approach beats staging a copy of the service, and previews a Part II walkthrough against HolmesGPT on a real GKE cluster.

    #testing#kubernetes
Jun 10•10m read time•From metalbear.com
Post cover image
Table of contents
What’s an AI-SRE? #Meet mirrord exec #Where mirrord fits #What your AI-SRE already owns #How to set it up #Why not just stage a copy of the service? #Try it #
1.2K Impressions
MetalBear's image
MetalBear

33 Followers

•

611 Upvotes

Would you recommend this post?

Copy link
WhatsApp
Facebook
X
New Squad
  • © 2026 Daily Dev Ltd.
  • Guidelines
  • Explore
  • Tags
  • Sources
  • Squads
  • Leaderboard