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.

Developer Tools Israel 2026.11.19
3.8pts

Detailed Notes

Pros 5 items

Mirrors remote pod traffic to a local process so local code handles real requests with 0 impact on live users
Copies in-cluster environment variables, DNS and network context, removing 90% or more environment drift
Connects with 1 command, requiring no application changes or extra services deployed
Proxies 2 read paths - filesystem and environment - so in-cluster mounts and configuration are reachable
Pairs an open source CLI with VS Code and JetBrains plugins across 2 editor families

Cons 4 items

Needs temporary cluster permissions, so enterprise security policies need review
Traffic mirroring adds network overhead, requiring care in latency-sensitive cases
Language and runtime support is still being completed
Team collaboration and governance live in the commercial edition

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

Visit mirrord Website → https://mirrord.dev/
Visit Website ↗