Run local processes in your Kubernetes environment without deploying, for seamless cloud-local development.
mirrord is a developer tool that allows you to run local processes in the context of a Kubernetes environment without deploying your code. It mirrors traffic, file operations, and environment variables from a target pod to your local machine, enabling seamless debugging and testing in cloud-like conditions. This solves the problem of needing to deploy untested code to staging environments for realistic testing.
Developers and DevOps engineers working with Kubernetes who need to debug, test, or develop applications locally while interacting with cloud resources. It's particularly useful for teams practicing cloud-native development.
Developers choose mirrord because it eliminates the deployment overhead for testing, reduces environment disruption, and provides a realistic cloud context locally. Its integration with popular IDEs and CLI offers flexibility and ease of use.
Connect your local process and your cloud environment, and run local code in cloud conditions.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Mirrors incoming traffic from a target pod and routes outbound traffic through it, enabling local processes to interact seamlessly with cluster network conditions without deployment.
Offers extensions for VS Code and IntelliJ with visual demos in the README, making it accessible for developers in their preferred environments.
Intercepts file operations and provides access to environment variables from the target pod, allowing local code to run as if in the cloud, as described in the key features.
Eliminates the need to deploy untested code to staging, speeding up development cycles, which is central to the project's philosophy.
Requires elevated Linux capabilities like CAP_SYS_ADMIN, which may not be permitted in secure Kubernetes setups, and disabling them can break functionality, as noted in the README.
Launches an agent pod on the cluster, adding overhead and potential interference with existing workloads, which is inherent to its architecture.
Managing disabled capabilities or custom setups can be tricky, and the README admits it might make mirrord unusable in some configurations, requiring careful tuning.