I like the debugging aspect of it, that you can forward requests with special header to your local environment. There is also another tool I came across when I had to troubleshoot how application behaves on production called rookout. The cool thing about this approach is that you can use step debugger in production environment without freezing the actual clients requests (internally it makes a copy of your prod app, which makes it possible), then you can see step by step what’s happening. This is only if I have to go with the paid version. Pretty useful stuff…Thanks!
Thanks for another great video, I didn't know about mirrord! It sounds promising but I don't really like the fact that the free version doesn't work well with multiple pods. You may want to be able to mirror apps already deployed with multiple replicas in a "pre-production" cluster just because that's the way they're deployed in production, and you want to have a way to balance your traffic especially if that app is shared among many. Still I believe that remote development is a great choice to fix many of the problems you listed in the video.
I think the free version of mirrord is a little more useful than your rating. For example, it's useful for occasional troubleshooting in a cluster. It can also be useful when debugging a single service that is running in a local cluster. (This is something else the documentation fails to mention.)
these new to me, i’ve been using kubectl port-forward + docker compose for the most part, production clusters always have really annoying restrictions in my experience, i think these may have issues as soon as a cloud service comes into the frame? which is basically always now. I think its still a hard / unsolved problem
We explored it together with a few other tools in the same category. Take a look at ruclips.net/user/liveYqmLIh31VH0?feature=share. It's not exclusively about telepresence but it might help.
Most of the tools that work remotely work in a local Kubernetes cluster as well, so I'll make a guess that you meant tools that are only for local development. If that's the case, mirrord and Telepresence are some of very few that are meant to be local-only (even that is only partly true). As for local Kubernetes itself, my favorites are Rancher Desktop if you prefer running it most of the time or KinD if you tend to create and destroy clusters frequently.
Appreciate the input!@@DevOpsToolkit - tried scanning some of your videos for your take on this, but didn't see anything. I am looking to run some demos in the near future to folks that are not so kubernetes-saavy and will be doing a lot of simple stuff on a local cluster running on my laptop so this is exactly what I'm looking for. Thanks!
mirrord.dev/docs/overview/faq/#how-is-mirrord-different-from-telepresence summarizes it well. Bear in mind that I normally do not reference "this vs that" from vendors since they're very biased and rarely honest in those but, in this case, I believe it's a fair list. The only note I would add is that some of those bullets applies only when compared with the mirrord for Teams version and that "mirrord doesn’t require you to install anything on the cluster." is not true (operator is installed in the cluster, even though it is not a requirement).
It doesn't looke like it does anything different than telepresence or czctl, the latter was my favorite but unfortunately their product is in an unusable state at the moment.
![OhGeesy x Lefty Gunplay - What It Iz [Official Music Video]](http://i.ytimg.com/vi/L0yzW9t2ixk/mqdefault.jpg)
What do you think of mirrord? Can it challenge Telepresence?
I like the debugging aspect of it, that you can forward requests with special header to your local environment. There is also another tool I came across when I had to troubleshoot how application behaves on production called rookout. The cool thing about this approach is that you can use step debugger in production environment without freezing the actual clients requests (internally it makes a copy of your prod app, which makes it possible), then you can see step by step what’s happening. This is only if I have to go with the paid version. Pretty useful stuff…Thanks!
Your ability to describe complex scenarios in an easy to understand way is very good 👍
This is exactly the problem I was trying to solve! Thanks again!
Thanks for another great video, I didn't know about mirrord!
It sounds promising but I don't really like the fact that the free version doesn't work well with multiple pods.
You may want to be able to mirror apps already deployed with multiple replicas in a "pre-production" cluster just because that's the way they're deployed in production, and you want to have a way to balance your traffic especially if that app is shared among many.
Still I believe that remote development is a great choice to fix many of the problems you listed in the video.
great video as always including the hard facts towards mirrord OSS cons 😂!
I used telepresence before and have this on my bucket list to try out!
Awesome!❤
I think the free version of mirrord is a little more useful than your rating. For example, it's useful for occasional troubleshooting in a cluster. It can also be useful when debugging a single service that is running in a local cluster. (This is something else the documentation fails to mention.)
these new to me, i’ve been using kubectl port-forward + docker compose for the most part, production clusters always have really annoying restrictions in my experience, i think these may have issues as soon as a cloud service comes into the frame? which is basically always now. I think its still a hard / unsolved problem
Thanks!
Thanks a ton.
Video is great 🎉, but comment for Weblogic rocks! Just to let you know there are some people stil using OAS in production 😂
Amazing video! Do you have any videos on telepresence?
We explored it together with a few other tools in the same category. Take a look at ruclips.net/user/liveYqmLIh31VH0?feature=share. It's not exclusively about telepresence but it might help.
What framework do you suggest for local kubernetes development work in 2024? Minikube, kind, k3s, etc.?
Most of the tools that work remotely work in a local Kubernetes cluster as well, so I'll make a guess that you meant tools that are only for local development. If that's the case, mirrord and Telepresence are some of very few that are meant to be local-only (even that is only partly true). As for local Kubernetes itself, my favorites are Rancher Desktop if you prefer running it most of the time or KinD if you tend to create and destroy clusters frequently.
Appreciate the input!@@DevOpsToolkit - tried scanning some of your videos for your take on this, but didn't see anything. I am looking to run some demos in the near future to folks that are not so kubernetes-saavy and will be doing a lot of simple stuff on a local cluster running on my laptop so this is exactly what I'm looking for. Thanks!
Great video as always 🙂
How about windows nodes, does mirrord supoort it?
It should work with WSL if not directly.
What are the cons of Telipresence? 🤔
mirrord.dev/docs/overview/faq/#how-is-mirrord-different-from-telepresence summarizes it well. Bear in mind that I normally do not reference "this vs that" from vendors since they're very biased and rarely honest in those but, in this case, I believe it's a fair list. The only note I would add is that some of those bullets applies only when compared with the mirrord for Teams version and that "mirrord doesn’t require you to install anything on the cluster." is not true (operator is installed in the cluster, even though it is not a requirement).
@@DevOpsToolkit Thank you. Really appreciate your content. 😄
Does mirrord work with Istio? Especially when mTLS is enforced
I haven't used it with istio yet. I'll try it out and get back to you.
# til
There is also "bridge to kubernetes". This is developed by Microsoft. So plugins for Visual Studio and vscode.
I haven't tried that one. Adding it to my to-do list.
enough with the hands
It doesn't looke like it does anything different than telepresence or czctl, the latter was my favorite but unfortunately their product is in an unusable state at the moment.