- If a dev writes to a DB, won’t that mess up others' tests?
mirrord enables concurrent usage of the same cluster through the following capabilities:

This raises some big questions:
- What happens when multiple developers use the same cluster? 👩🏿‍🤝‍👨🏼
- If one dev steals traffic from a service, does that block others?🚦
- If a service reads from a queue, will one dev steal all the messages? 📨

This means🧵 👇 :
✅ Immediate effect on queues & traffic.

✅ A stable, high-level Kubernetes API solution.

✅ No reliance on container runtime internals.

📢 Read the full story on how we built—and deprecated—our container pause feature in this article by @Aviramyh: https://buff.ly/3CHK3uP

➡️ New File Operation Support – Huge thanks to @facundopoblete for adding support for rmdir, unlink, unlinkat, and statfs! 👏

A big shoutout to our amazing community for making mirrord even more powerful! 🎉
Try out the latest updates, and let us know what you think.

➡️ Prometheus Metrics Export – Export mirrord agent metrics for improved observability and debugging.

➡️ mirrord CLI Improvements – Thanks to @waveywaves, the `-f / --config-file` argument now assumes `./.mirrord/mirrord.json` by default! 👏

➡️ IPv6 Support – Expanded support for outgoing traffic, incoming traffic interception, and domain name resolution. (Mirroring in progress!)

➡️ Kubernetes Service as a Target – Mirror traffic from an entire Kubernetes Service, making debugging multi-replica workloads easier.

➡️ mirrord Policies – Gain initial controls for file operations, offering more flexibility in managing remote file interactions.

➡️ IntelliJ Plugin Namespace Selection – No more manual switching! Select your Kubernetes namespace directly in the target selection dialog.

➡️ How to use the mirrord policy:

If you want to block stealing traffic on all webserver deployments in a namespace, you can write a policy like this:

➡️ Controllable Features🔧

Some policies don’t block features outright; they override user configurations:

- Env Policy: Controls which environment variables can be retrieved.
- FS Policy: Controls which files can be accessed or how they can be opened (e.g., read-only, local, etc.).

➡️ Blockable Features 🚫

You can use mirrord policies to block the following features:

- steal: Prevents stealing traffic from targeted pods.
- steal-without-filter: Same as above, but only if no HTTP filter is used.
- mirror: Prevents mirroring traffic.

➡️ What are mirrord Policies?

When you install the mirrord operator, it creates two types of policies that have the same specifications:

- MirrordPolicy: Applies to targets in the same namespace.
- MirrordClusterPolicy: Applies to targets across the entire cluster.