Only ~4 more hours until @aviramyh and @RinkiyaKeDad ‘s webinar, including a live demo of a Cursor agent iterating and self-correcting against k8s. Let’s hope it works! Sign up here: https://t.co/hYsmXOXNii
What's mirrord good at? Verifying code in real-world conditions, fast.
When is this useful? All the time, but especially when production is on fire, you have a proposed fix, and you want to be sure it'll actually put out the fire rather than pour gasoline on it.
AI-SREs are getting good at proposing fixes when alerts fire. The missing piece is knowing whether the fix actually works before it reaches production.
Right now there's no good answer. You have to deploy to staging to know if it works, which is slow. In our latest blog Eyal Bukchin wrote about how to fix this problem: automatically verify every suggestion against your real cluster (without deploying) before it reaches a human using mirrord.
This way:
❌ Fixes that don't pass don't get reviewed.
✅ Fixes that do come with a verdict already attached.
This approach works regardless of the tools you're using (@resolveai, @datadoghq Bits, HolmesGPT by @RobustaDev, or some in-house solution!)
Link to read the blog is in the thread
We'll be at @awscloud Summit Sydney next week on 13–14 May!
Working with AI coding tools? Kubernetes? Both? Come say hi 👋 and we’ll show you how mirrord helps Kubernetes teams fully leverage the productivity benefits of AI-driven development!
Yesterday we hosted Ryota Sawada, the Release Lead for #Kubernetes 1.36, for a webinar!
In case you missed it, you can now check out the recording on YouTube. It was a really interesting discussion where Ryota talked about:
- New and exciting features in Kubernetes 1.36
- Where he sees Kubernetes as a project heading towards in future releases
- His experience being part of the release team since Kubernetes 1.32
- How the release team works and why you should consider applying
Watch here: https://t.co/TVfdAV00SE
And if you'd like to read about the latest features in 1.36, read the blog: https://t.co/d3m73NUwVq
Windows support for the mirrord VS Code extension is coming, and early access is open now! 🪟
To try it, search for "mirrord" in the VS Code (or Cursor, or other VS Code-based IDEs) extension marketplace and download it. Then hop on our Slack and tell us about your experience!
mirrord community Slack: https://t.co/7CZO9dWlI2
When we started mirrord, most teams were skeptical that engineers could test instantly and concurrently on a shared staging cluster. So they settled for waiting on CI and fighting for staging access.
Four years and 5,000 GitHub stars later, that's changed. Companies like @mondaydotcom and @SurveyMonkey have hundreds of developers testing concurrently on shared #Kubernetes clusters every day. And now with #AI generating 10x more code and the bottleneck shifting to validation, instant concurrent testing isn't a luxury anymore - it's a necessity for any company that wants to ship at the pace AI enables.
If you're one of the 5,000, thank you! If you're not: https://t.co/mO7QbyaZd5
AI writes the code. But who catches the bugs?
Less typing, more reviewing. That's the new developer reality.
@olensmar, CTO of @testkubeio, breaks down how to get ahead of quality issues from AI-generated code. Prompt engineering, context engineering & continuous testing across your entire SDLC.
Full talk 👇
https://t.co/j4omitPtHw
“Before mirrord, a lot of developers were afraid of setting up their local development setup. I think mirrord removed that fear.”
— Shahar Golan, DevOps Engineer at @mondaydotcom
At https://t.co/DwgEzCP01D, mirrord helped remove the friction around local development, making it easier for hundreds of engineers to start writing code without worrying about setting up complex dev environments.
The results speak for themselves:
- 245+ engineers developing on a shared cluster
- Onboarding new developers in about 1 hour instead of 3–5 days
- Environment setup that takes seconds, not half an hour
- Dev environments that cost $0 in cloud spend
Read the full story 👇
https://t.co/eqQ83NQR5Z
this is super exciting. https://t.co/JYtX9SuEUb didn’t buy our vision at the beginning, but slowly became more open to it, and now it is how engineers develop. read the case study
There's a lot of noise around how "Ai generates buggy software". The truth is writing the code was always 20% of the time. Testing and refining was always 80%. But now as that 20% compresses 10x, we want to compress the 80% as well... That's the mistake.
MetalBear is launching a new tool that allows development teams to run CI tests against Kubernetes environments without needing to deploy code to it or spin up test environments. https://t.co/3ZE39Fl5hR
▶ In this workshop, we’ll show how to test AI-generated code directly against your K8s environment without deploying.
You’ll see a live demo using Cursor + mirrord to get fast, real feedback safely.
Register now! https://t.co/PoYtL6ok0r
#kubernetes#devops#sre#ai#genai
Happy #Kubernetes Release Day to those who celebrate!
We understand that going through the entire release notes can be overwhelming, so we've cherry-picked a list of our favorite features from the Kubernetes 1.35 release, along with examples showing how to try some of them out.
Read here: https://t.co/vSOez856iP
@nise_nabe If I understood correctly and you want to have a different mirrord config per run configuration, then note you can control it with the MIRRORD_CONFIG_FILE env var.
So for every run configuration, you can set MIRRORD_CONFIG_FILE pointing to a different mirrord config file.
Cloud-Native Dev Is Broken. mirrord Is the Fix.
Welcome back to The Cloud Computing Insider! Today, I'm diving deep into a tool that's changing the game for cloud-native developers: mirrord.
Cloud-native development comes with real challenges — from complex remote environments and slow feedback, to “it works on my machine” bugs that seem to haunt every release. Sound familiar? That’s where mirrord steps in to help.
mirrord brings the power of production-like development straight to your local machine. With it, you can access real cloud resources, test integrations, and debug faster—without waiting for slow pipelines or risking your live environments. No more endless deployment waits or fragile staging setups. Just rapid, safe, and smart iteration.
What makes mirrord special?
Test locally with production-like accuracy: Run your code on your machine, but interact directly with cloud resources.
Seamless debugging: No need to mock or replicate massive backends. Debug API integrations and see real data—all from your IDE.
Faster feedback: No more waiting on CI/CD pipelines. Debug directly from your IDE of choice, see the impact, and iterate at the speed your team demands.
Team-ready: leverage features like http-filtering and db branching enabling you to work in a shared cluster without disrupting the work of others teammates sharing staging resources.
I've heard from developers across the community who now save hours every week, run into fewer surprises in production, and feel truly in control of their feedback loops. The energy around mirrord is real, and the community is growing fast!
Want to give it a try? Get started here:
👉 mirrord Docs: https://t.co/9Rqv1RBjeL
👉 mirrord GitHub: https://t.co/Y2CMEi4DYc
👉 Join the mirrord Slack: https://t.co/xf9jQ1wFlz
Tell me about your own experiences and questions in the comments below! If you found this helpful, hit subscribe—and if you’re ready to stop worrying about “it works on my machine,” check out the links above and make mirrord part of your workflow today.
🍸 Wrap up your first day at #KubeCon with us!
We’re co-hosting a Happy Hour with our friends at @diagridio on Tuesday, Nov 11 right after the KubeCrawl. Good food, great drinks, and a room full of interesting people in the Kubernetes space!
It’s the perfect way to unwind after a full day of sessions and connect with folks building the next wave of developer tools.
👉 Sign up for the happy hour here: https://t.co/5jGvkHs2yC
Attending #KubeCon Atlanta? 🇺🇸
With hundreds of sessions at the conference, it can get really confusing figuring out which talks to attend.
So @RinkiyaKeDad from our team went through the schedule and picked out a few talks that stood out. Give it a read as it might help you narrow things down or discover a session you’d otherwise miss!
https://t.co/fHUyubAbHQ
Recently we hit a tricky Terraform schema bug in the mirrord Operator. What impressed us most wasn’t just that @claudeai fixed it, but how it wrote its own debugging script to help understand the problem!
Read the blog to learn more how it all unfolded:
https://t.co/HZ3fpvsRcb
If your app uses queue services like Kafka or Amazon SQS, how do developers access them during development?
Watch this video to learn how the queue splitting feature in #mirrord lets multiple developers safely test against the same queue without conflicts 👇