JAKUB KRZYWDA

@jakubkrzywda

vs

Kubernetes Istio

TRAFFIC ROUTING
Kubernetes traffic routing is
implemented using Ingress,
Service and Pod resources.

JAKUB KRZYWDA
@jakubkrzywda
 An Ingress is used to
expose Services to
clients outside the
Kubernetes cluster

Service provides a
rudimentary load
balancing of incoming
requests

Application ports are

exposed by containers
running in Pods

External
Application
Traffic

Traffic
Routing

JAKUB KRZYWDA
@jakubkrzywda
Istio traffic routing is
implemented using Envoy
Proxy, Destination Rule,
Virtual Service and Gateway
resources.

JAKUB KRZYWDA
@jakubkrzywda
Gateways handle the
incoming and outgoing
traffic
Gateway

Virtual Services allow

defining sophisticated
traffic distribution rules

Virtual Virtual
Service Service

Istio Destination Rules

allow defining subsets of Destination
Rule
Destination
Rule
Destination
Rule
Destination
Rule

endpoints

External
All traffic sent and Traffic

Traffic
received by applications Application
Routing

is proxied through Envoy Envoy Proxy

Service
Discovery

JAKUB KRZYWDA
@jakubkrzywda
K8S vs ISTIO TRAFFIC ROUTING

Gateway

Virtual Virtual
Service Service

Destination Destination Destination Destination

Rule Rule Rule Rule

External
Application Application
Traffic

Traffic Service
Envoy Proxy
Routing Discovery

JAKUB KRZYWDA
@jakubkrzywda
 JAKUB KRZYWDA
@jakubkrzywda

THAT’S IT FOR TODAY!

My name is Jakub Krzywda.

I’m a Senior Cloud Native Engineer and

Kubernetes Trainer.

I post about: Kubernetes, Cloud Native

technologies and DevOps practices.
 JAKUB KRZYWDA
@jakubkrzywda

WHAT DO YOU THINK?

Do you use Istio or other service mesh in your
Kubernetes cluster? Or have you considered
adding it, but opted against it? What were your
main decision drivers?

Remember
to click
follow + 🔔