This video is the third installment of Istio Service Mesh. If you are new to Kubernetes Service Mesh and want to know in more detail, what issues a Service Mesh such as Istio or Cilium resolves, please watch, my first Istio video here: ruclips.net/video/x_HRl-Ehvb8/видео.html.
For the first time with one of your videos, I'm not impressed and didn't watch very much of it. And maybe that's because I don't understand what problem this solves. Why is this a good idea? What are the alternatives? When would you install this? I can't watch a video on how to set up Istio, if I don't know why I would do it.
Ok, let's break down your comment, you don't understand what the problem this is supposed to solve? You must have missed the very first section that briefly discusses what a Service Mesh is. If you are new to the Service Mesh, perhaps it would be a good idea to watch the original Istio video or the Cilium service mesh. Istio is one of the pioneers of the Service Mesh idea. However, up until now, they have used sidecars to implement the service mesh. This means for every Pod you deploy, Istio injects an additional container that manages L7 load balancing, routing, retries, etc. This will increase overheads, especially in large Kubernetes environments. With Ambient Mesh (the topic of this video), Istio is doing away with sidecars. This video discusses how the new architecture works. I've also provided a comparison with Cilium's Service Mesh. For teams that have already committed to Istio, switching to Ambient Mesh is probably a smoother way of eliminating sidecars than switching to a different service mesh such as Cilium.
@@TheLearningChannel-Tech Ok, it's a fair answer that this is actually not the right video to watch, if I'm looking for info on what problem Istio solves. Thank you. I'll try the other one.
@@bothorsen4292 Hi Bo, this video hopefully provides you more details on what problems service mesh providers such as Istio are trying to resolve: ruclips.net/video/x_HRl-Ehvb8/видео.html. Hope this helps. If you have any questions please don't hesitate to post. Thanks.
This video is the third installment of Istio Service Mesh. If you are new to Kubernetes Service Mesh and want to know in more detail, what issues a Service Mesh such as Istio or Cilium resolves, please watch, my first Istio video here: ruclips.net/video/x_HRl-Ehvb8/видео.html.
always awesome tutorial video
Thank you! Cheers!
Awesome. Thanks
Welcome.
For the first time with one of your videos, I'm not impressed and didn't watch very much of it. And maybe that's because I don't understand what problem this solves. Why is this a good idea? What are the alternatives? When would you install this?
I can't watch a video on how to set up Istio, if I don't know why I would do it.
Ok, let's break down your comment, you don't understand what the problem this is supposed to solve? You must have missed the very first section that briefly discusses what a Service Mesh is. If you are new to the Service Mesh, perhaps it would be a good idea to watch the original Istio video or the Cilium service mesh.
Istio is one of the pioneers of the Service Mesh idea. However, up until now, they have used sidecars to implement the service mesh. This means for every Pod you deploy, Istio injects an additional container that manages L7 load balancing, routing, retries, etc. This will increase overheads, especially in large Kubernetes environments. With Ambient Mesh (the topic of this video), Istio is doing away with sidecars. This video discusses how the new architecture works. I've also provided a comparison with Cilium's Service Mesh. For teams that have already committed to Istio, switching to Ambient Mesh is probably a smoother way of eliminating sidecars than switching to a different service mesh such as Cilium.
@@TheLearningChannel-Tech Ok, it's a fair answer that this is actually not the right video to watch, if I'm looking for info on what problem Istio solves. Thank you. I'll try the other one.
@@bothorsen4292 Hi Bo, this video hopefully provides you more details on what problems service mesh providers such as Istio are trying to resolve: ruclips.net/video/x_HRl-Ehvb8/видео.html. Hope this helps. If you have any questions please don't hesitate to post. Thanks.