PROVIDER - Mirror cluster traffic to a local process
mirrord
mirrord mirrors remote pod traffic to a local process so local code serves real requests without touching live users, copying cluster environment and DNS in 1 command with no code changes; the boundaries are temporary permissions and mirroring overhead.
3.8pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
mirrord is a Kubernetes development tool from MetalBear whose core capability is traffic mirroring plus environment replication: a local process receives a remote pod's traffic and inherits the cluster's networking and environment context.
In the development tools category it is transparent remote debugging: far less intrusive than rewriting deployments or installing proxies, it delivers near-production debugging on a laptop.
Key Strengths
- Traffic mirroring: real requests reach the local process
- Environment copy: cluster DNS and variables available
- No rework: 1 command, no code changes
- Filesystem proxy: read in-cluster mounts
- Editor integration: VS Code and JetBrains
Product Ecosystem
Platform capabilities
Traffic mirroring, environment variable injection, DNS and network proxying, filesystem reads, target pod selection and scoped permissions.
Integrations
Works with kubectl, Kubernetes, VS Code, JetBrains, local debuggers and CI systems.
Typical scenarios
Local microservice debugging, production issue reproduction, cluster dependency integration and onboarding to real behaviour.
Limitations
- Permission needs: temporary cluster rights
- Network overhead: mirrored traffic consumes bandwidth
- Runtime coverage: some languages are still catching up
- Governance tiers: team features are commercial
Use Cases
- Debugging real traffic locally (★★★★★): closest to production
- Production issue reproduction (★★★★☆): observe real requests safely
- Strict permission environments (★★☆☆☆): review security policy first
- Fully offline development (★☆☆☆☆): not applicable
Pricing
| Item | Price | Notes |
|---|---|---|
| Open source CLI | $0 | MIT licence, commercial use allowed |
| Editor plugins | $0 | Free to use |
| Commercial edition | Contact sales | Team governance and central configuration |
FAQ
Does it affect live requests?
The default mirror mode delivers requests to both the original pod and your process; steal mode takes over traffic and must be used carefully.
Do I need to change deployments?
No, the tool accesses target pods client side through cluster permissions.
Which languages are supported?
Mainstream languages work; check the official documentation for exact coverage.
How do I bound permissions?
Target a specific namespace and pod, and narrow authorization through cluster RBAC.
Code Examples
# Install the CLI on macOS
brew install metalbearco/tap/mirrord
# Mirror traffic from a target pod and start the local process
mirrord exec --target deployment/demo-api -- npm run dev
# List available targets
mirrord ls
// .mirrord/mirrord.json (excerpt)
{
"target": "deployment/demo-api",
"feature": {
"network": { "incoming": "mirror" },
"env": { "include": "DEPLOYMENT" }
}
}
Community & Resources
- Website: https://mirrord.dev/
- Source repository: https://github.com/metalbear-co/mirrord
- Documentation: https://mirrord.dev/docs/
Articles
- 01 GitLab CI/CD Best Practices: From Beginner to Production-Grade Pipelines 07-18
- 02 Prometheus Monitoring System Setup: From Metric Collection to Alert Notifications 07-18
- 03 Ansible Automation Ops Guide: From Configuration Management to Application Deployment 07-18
- 04 Docker Beginner Tutorial: From Installation to Containerized Web Deployment 07-18
- 05 API Integration Guide: REST vs GraphQL Comparison and Selection 07-18
- 06 GitHub Actions CI/CD Tutorial: Automated Build, Test, and Deployment 07-18
- 07 Docker Compose Multi-Container Deployment: Building Complete Application Orchestration 07-18
- 08 Kubernetes Deployment Guide for Beginners: Building a K8s Cluster from Scratch 07-18
- 09 Best VS Code Extensions 2026: Boost Your Development Productivity 07-18
- 10 Frontend Toolchain 2026: Vite / Next.js / Tailwind CSS Ecosystem 07-18