mirrord vs. Telepresence | Develop Locally with Your Kubernetes Environment mirrord vs. Telepresence - mirrord

Why choose
mirrord over Telepresence?

mirrord and Telepresence both let you run your code locally in the context of your Kubernetes cluster... so what makes them different?


mirrord works by injecting itself into your local process and overriding low level functions, like traffic and file access, which it then proxies to Kubernetes. This lets it easily connect any binary to Kubernetes, and also:

mirrord

No root access needed

Nothing installed on your cluster

Supports traffic mirroring as well as interception

Support granular configuration for what is executed on the cluster and what stays local

Telepresence

Requires root access on your machine

Requires a persistent deployment running in your cluster

Doesn’t support traffic mirroring

Connects your entire machine to the cluster

But above all... it just works!

  • @DyNATO: We switched from Telepresence to mirrord a few months ago due to instability and breaking updates in Telepresence. Wish I had known about mirrord before.

  • @Jörg Rosenauer: Fantastic plugin. Being able to run your service "locally in the cluster" through the click of one button is powerful. I have started to roll it out to the whole dev team. Also shout-out to the devs for being really helpful, had a very specific issue because of the way I set up my pods and it got fixed next day.

  • @IAmBabau: One underappreciated feature of mirrord is that in my experience it "just works" while I always have to spend way too much time configuring telepresence.

  • @Natan Yellin: mirrord from MetalBear really is magic Developing Robusta Dev locally used to be a pain. Robusta needs to access Prometheus in-cluster, to receive events on push with webhooks, etc.

    But with mirrord it just works. Seriously magical experience.

  • @msanteler: This is amazing

  • @Bar Hochman: I'm using it for around a month now. mirrord enabled me to easily connect my app into my k8s cluster and use the system as it in the k8s environment with ease. I could just forget running docker on my machine and use the dev k8s environment to run my code with minimal configuration and work.

  • @Danny Rehelis: After trying Telepresence, Gefyra and other, I can say with confidence this is by far, a surprise tool. It's like magic, an out-of-the-box experience like no other. Bootstrapping our development cycle, dropping the use of "local-dev", comes with fine-grained configuration. A real gem!

  • @castaneai: I tried using mirrord for Agones GameServer. Unlike Telepresence, which does various services, you can directly enter the Pod, so you can mirror the communication! wonderful

  • @angryundead: This… is really really cool.

  • @0merxx: Well on this unrelated occasion - thank you for mirrord! A life saver when writing controllers for k8s and need the cluster context. I don't know if usecase is common, but it fixed me :)

  • @Patrick Kerwood: After trying Telepresence, Gefyra and other, I can say with confidence this is by far, a surprise tool. It's like magic, an out-of-the-box experience like no other. Bootstrapping our development cycle, dropping the use of "local-dev", comes with fine-grained configuration. A real gem!

  • @Shani kaneti: An amazing product. For the first time I was able to debug my kubernetes pods, and all in such easy configuration and process. Recommended!!! Looking forward for the next releases

  • @Sam Krew: After telepresence, i love your product! Everything (or almost everything) works like a magic.

  • @Ahmet Enes Bayraktar: It is all magic, can't recommend enough!

  • @chanita kerrigan: This is a very very useful plugin that will allow you to debug your code locally but in the context of your k8s cluster using real traffic from the cluster in a frictionless way. IMHO it's also superior (in terms of ease of use/value) to other solutions out there. 5/5