From linux namespaces to ServiceMesh: DeepDive

Transcript

1. training@container-solutions.com www.container-solutions.com ServiceMesh Deep Dive From linux kernel namespace till ServiceMesh
2. Who am I? Where are you? Dawid Ziolkowski Cloud Native Engineer DawidZiolkowsk5 dawid.ziolkowski@container-solutions.com
3. Let’s talk ServiceMesh From the beginning...
4. … from the very beginning ;) … from the very beginning ;)
5. Step 1… bare metal
6. Step 2… VMs
7. Step 3… containers
8. Exercise
9. Still step 3… what’s inside these containers?
10. Step 4…. Service Mesh
11. What is a Sidecar? • Container which acts as man-in-the-middle between microservice and network • It hijacks all the traffic coming to/from your container • That’s why there is no need for application code change in order to start using service mesh • Can be automatically injected into your microservice pod
12. What REALLY is a Sidecar? • C++ based L4/L7 proxy • Very low memory footprint • It has been proven to run on 10,000+ VMs
15. “there is no such thing as a container” @Linux kernel
16. “Container” -> process isolated by namespaces
17. “Pod” -> multiple processes partially isolated by namespaces
18. Ok… convinced. But which service mesh to choose?
19. Istio LinkerD Kuma
20. Istio LinkerD Kuma - Does everything - Has few UIs - Most feature rich - Installs everything - Everything preconfigured out-of-the-box - You get not only service mesh but few extras - Does what service mesh suppose to do - Has simple UI - Many features but some things are still missing - Installs Prometheus/Grafana too - Also easy to start from day 1 - Does not do everything for you - Does not have a UI - You can do a lot but you need to do it yourself - Installs nothing extra - Plain service mesh - Doesn’t do much out of the box which means it can be very well tailored
21. Thank You! Happy service meshing :)