Service Mesh In Kubernetes Explained

What is a service mesh in Kubernetes? What are it's features? When should we use a service mesh? Why do we need service mesh? Let's answer those and other questions related to service mesh?

#servicemesh #kubernetes #k8s

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ Timecodes ⏱ ▬▬▬▬▬▬
00:00 What did we have in the past?
01:54 What do we have now?
03:14 Service discovery
04:45 What is service mesh?
05:44 How does service mesh work?
09:33 Service mesh feature

[DevOpsToolkit]

Are you using a service mesh? If you are, which one did you choose and why?

[ariskaraiskos]

i was searching for more than a year for a video that simply explains the features of service mesh vs what k8s offers out of the box, this video its simply outstanding!

[jnrc]

Thanks Viktor, I have shared this video with my coworkers here in Mexico as we are launching or first Kubernetes platform. For non-english speaking countries your English is really clear and useful. Keep going!

[ankit_adarsh]

Awesome! Linkerd vs Istio would be great!

[mysticaltech]

Victor, you are my Kube teacher, thank you so much! Love your teaching styles and content! 🙏

[wollginator]

Thanks for the overview, Linkerd vs Istio would be a nice and helpful comparison!

[ijayeti]

The is the best explanation of service mesh I’ve seen

[sergiocardenas]

we implemented linkerd, fast and simple; cant be more happy with it. documentation can be improved, though it covers most scenarios. I would suggest istio vs linkerd, and see where the magic always happens.

[StephaneMoser]

Nice vídeo, you made a great job summarizing this topic. I would love to see the comparison between istio and linkerd

[sajithvenkit]

Thank you for yet another great video. Looking forward to see a follow-up session comparing linkerd and istio

[kulinskyvs]

Comparing service mesh implementations would be really interesting!

[Peter]

You put it very well, "Networking is typically more important than majority of the ppl think it is"! I'd argue that value that service mesh brings and actually even Kubernetres itself is "just" encapsulating complex networking concepts and making it work for specific purpose. Also, Linkerd vs Istio vid would be great

[kevinyu]

BTW, Knative is built on top of Service Mesh, specifically Istios. In addition, it provides a good solution for auto-scaling or scaling-to-zero, which is very handy in many scenarios.

[steshaw]

Yes, please do compare devices meshes. Particularly Istio and Linkerd but also if there are tangible reasons to consider others.

[mcgowan]

Great Explanation, so clear. another +1 for deep dive or comparison featuring Istio

[anshuman]

Appreciate it. Concepts are cleared. Hope soon one practical tutorial come on it.

[Blkhole]

Not using a proper one at the moment, services and the ALB Ingress controller provided by Amazon do the trick for us, at least for now. However, my previous client's infrastructure was heavily dependent on Istio (running a multi-region / multi-language ad search portal with a pretty complex routing logic), up to the point where 60% of my work day consisted of writing virtual services and routing rules for Istio. I find it to be a bit of a double edged sword - while Istio had far more features than Consul or Linkerd at the time (mid 2019), it lagged behind slightly in terms of speed, at least according to the benchmarks we ran back then. Also, the learning curve and overall complexity was among the highest of any tool that I've worked with. Can't remember the last time a piece of software made me feel that dumb.

[smerlos]

I am implementing linkerD reason? CNCF

[apoloniaturk]

Beautiful video. Do you have anything similar that focuses on security protocols that tend to be used, such as SSH, and newer stuff?

[mdaverde]

A particular way I'm not a fan of the cloud native philosophy is that it makes it seem like some practices are "features" when I'm not so sure.

For example, autoscaling tends to be a baked in feature in many cloud native technologies such as kubernetes clusters and serverless. It seems to be by default a good thing. But why? Autoscaling in some circumstances can be a response to a symptom of underlying problem such as a DDoS attack or an application performance failing or network latency issues. We also are under financial confines. It's not to say that these projects say explicitly you shouldn't spend time root causing the need to autoscale but I do feel like our industry as a whole don't hold these practices in skepticism for too long before making them widespread. Latency-aware load balancing is a service mesh feature that I'm skeptical of.