Mirror on the Wall, How Many K8s Environments Are Enough After All?
summary
Claims that Mir lets teams stop provisioning per-developer and per-CI clusters and instead mirrors traffic to a local process while using a single staging cluster; demo uses VS Code/CLI integration, breakpoints, and a live request to read a cluster file and return a modified response proving it works. Features include steal mode with HTTP filters, queue splitting for concurrent consumers, and safety policies to block writes to sensitive DBs, all aimed at lowering cloud costs and operational overhead.
AI-written summary · about
chapters (9)
- 0:00Introduction and Overview
- 0:51Initial Excitement and Early Challenges
- 1:36Scaling Issues and Rising Costs
- 3:38The Downside of Multiple Clusters
- 5:07Introducing Medi: The Solution
- 5:44How Medi Works
- 8:03Demo: Medi in Action
- 19:44Advanced Features of Medi
- 21:57Conclusion and Final Thoughts
related talks
27mMirror Mirror on My local machine
36mTesting in Production – Mirroring CQL Traffic to a Shadow Cassandra Deployment
26mClosing the Developer Experience Gap of K8s Development
51mEnabling Developers in a Multi-Cloud World
49mDeveloping microservices applications on the Kubernetes platform
24mIf Your Application is Going to Run in a Multi-Node Cluster, Why Are You Develo...
01h 01mIstio Service Mesh & pragmatic microservices architecture
36mDesigning Staging Environments