How Service Meshes Work in Kubernetes

[@e529]

The part where you described Service Mesh as the E-W load balancing as opposed to Ingress N-S load balancing made everything click, thank you!

[@rossbrunson5122]

Yeah, that was the ticket, all the rest was suddenly transformed from "blah blah" to "oh wow, why didn't anyone ever say that!"

[@mdk1983]

Very well explained. Now I understand why many speakers who write on these invisible boards are wearing black or dark costume.

[@CharlesRyu]

you are my favorite youtube channel rn

[@kentkits]

Short and crisp! Thanks!

[@busaram]

Super helpful. Thanks so much for making this.

[@kisan-majdoorkalyansamiti7390]

First thing, if s1 is going to call s2 time of design it is clear both communite or not if both are in same intranet no worry about internal security as both in private subnet if both are in diffrent then difffrent security mechanism. It is also like esb onky think creating multiple esb ( proxy) It has pros and cons as increasing too much proxy also increasing manageability. We can easily do all these thinks in interceptor and no need of extra complexity of service mesh

[@Babbili]

tell me where did you got your Tee from

[@jackgao8861]

Nice video

[@victornoagbodji]

🤔 well all that sounds a lot like what an application level proxy would do right? 🤔

[@alexk581]

Can someone explain why first of the yours Microsoft youtube videos have disabled comments? This is the very first one I found which has open comments. Why is this? Why you do not wanna people have an open discussion?

[@scottstensland]

probably the 99% shutoff and 1% enabled model just to test the waters on level of comments VS noise

[@chaus0808]

@@scottstensland haha lol, underrated comment