2 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
Mirrord allows developers to run local processes in a Kubernetes context without deploying to the cloud. It connects your local environment to a selected pod, mirroring traffic and file interactions. Available as a VS Code extension, IntelliJ plugin, and CLI tool.
If you do, here's more
mirrord allows developers to run local processes within their Kubernetes environment, offering a way to test code without deploying it to the cloud. This tool is available as a Visual Studio Code extension, an IntelliJ plugin, and a CLI tool. Developers can debug their projects by selecting a Kubernetes pod to impersonate, which means their local processes can interact with the pod as if they were running directly in the cloud environment. This setup mirrors traffic and environment variables between the local process and the selected pod, streamlining the development process.
To get started, users need to enable mirrord in their chosen IDE and follow a few simple steps to begin debugging. Installation options include Homebrew, a shell script from GitHub, and community-maintained Nix packages, though Windows support is limited to WSL. When running a local process, mirrord requires certain Linux capabilities to function properly, such as CAP_NET_ADMIN and CAP_SYS_PTRACE. Users can disable some capabilities if needed, but doing so may restrict functionality.
The article also emphasizes community involvement. Users are encouraged to check out open issues, contribute to the project, or ask questions via Slack. There's a mention of an ADOPTERS.md document showcasing how various organizations utilize mirrord, inviting others to share their experiences. Lastly, a fun aspect of the article is the inclusion of a password for a raffle at KubeCon Atlanta, adding a personal touch to the technical content. The project prioritizes a safe community, highlighted by a call to review the Code of Conduct.
Questions about this article
No questions yet.