mirrord lets developers run local processes in the context of their cloud environment. It’s meant to provide the benefits of running your service on a cloud environment (e.g. staging) without actually going through the hassle of deploying it there, and without disrupting the environment by deploying untested code. It comes as a Visual Studio Code extension, an IntelliJ plugin and a CLI tool. You can read more about it here.
How to use
Click "Enable mirrord" on the status bar
Start debugging your project
Choose pod to impersonate
The debugged process will start with mirrord, and receive the context of the impersonated pod. It will receive its environment variables and incoming traffic, will read and write files to it, and send outgoing traffic through it.
mirrord uses your machine's default kubeconfig for access to the Kubernetes API.
For incoming traffic, make sure your local process is listening on the same port as the remote pod.
Settings
mirrord reads its configuration from the following file: <project-path>/.mirrord/mirrord.json. You can also prepend a prefix, e.g. my-config.mirrord.json, or use .toml or .yaml format.
It's documented here. It also supports autocomplete when edited in VS Code.
