Have a new entry on mirrord (https://mirrord.dev/) and how it mirrors a process from your local machine to Kubernetes. In this post I particularly talk about the mirrord agent but in the subsequent one, I will also be discussing about the tools you need to employ if you had to make this possible for yourself. Mirrord mirrors (and can steal) traffic from your Kubernetes environment to a local process which is the coolest part about it. Can't wait to talk more about it in the next one.
This is a huge security risk (both from a personal and desktop malware perspective), so I assume most people are only allowed to use it in staging. How many bugs reproduce in staging, though?
Not only do more bugs reproduce in staging than locally (for obvious reasons), but mirrord also saves you the trouble of figuring out how to run your stuff locally in the first place.
Previously, before you could add a single line of code to your microservice, you had to be able to run it and all of its dependencies on your local machine. This is such a huge challenge in some cases that people actually prefer to git push and deploy to the cloud for every little change.
With mirrord you can just clone the repo and debug.
