This document discusses Istio, an open source service mesh that provides traffic management, telemetry and security for microservices. It notes that as microservices grow in complexity, they require features like load balancing, monitoring and failure recovery. Istio addresses this by providing a service mesh layer that handles these functions and allows developers to focus on business logic rather than infrastructure. The document outlines Istio's key features such as automatic load balancing, rich routing rules, access controls, metrics and tracing. It also describes Istio's architecture, including its control plane that manages configuration and a data plane where Envoy proxies handle traffic.

1. Istio
Diego Pacheco

2. About Me

4. Kubernetes Architecture

5. Features Vs Concepts

6. Istio and Modern Cloud Deployments
❏ 1 Wave == NetflixOSS
❏ 2 Wave of Microservices
❏ Cloud Benefits
❏ Devops Struggle
❏ Multi-Cloud / Poly-Cloud
❏ Reduce Infrastructure Complexity
❏ Istio Provide Service Mesh Capabilities
❏ Solution on the Platform not on the
Application
❏ Istio provide Observability
❏ Microservice developer can focus on the
business rather than on the stack.

7. “service mesh is used to describe the
network of microservices that make up
such applications and the interactions
between them”
Service Mesh

8. Service Mesh Growth == Complexity
“Requires discovery, load balancing,
failure recovery, metrics, and monitoring.
A/B testing, canary releases, rate
limiting, access control, and end-to-end
authentication”

9. Istio | Features

10. ❏ Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic.
❏ Fine-grained control of traffic behavior with rich routing rules, retries, failovers,
and fault injection.
❏ A pluggable policy layer and configuration API supporting access controls, rate
limits and quotas.
❏ Automatic metrics, logs, and traces for all traffic within a cluster, including
cluster ingress and egress.
❏ Secure service-to-service communication in a cluster with strong identity-based
authentication and authorization.
Istio | Features

11. Istio | Design Goals
❏ Maximize Transparency
❏ Program network layer to route traffic
❏ In k8s the proxies are injected into Pods
❏ Traffic is captured by programing iptables rules
❏ Imcrementability
❏ System Growth and Add more Features
❏ Policies Enforcements
❏ Portability
❏ Run in any cloud or on-premises
❏ Deploy on multiple cloud for redundancy for instance
❏ Policy Uniformity
❏ Police api provides great control over the mesh
❏ i.e : Quota over CPU for ML Training. Separation between proxy and Policy.

12. Istio | Architecture - Control Plane

13. Istio | Architecture - Data Plane
Data Plane
+
MIXER

14. Envoy by Lyft
❏ Dynamic service discovery
❏ Load balancing
❏ TLS termination
❏ HTTP/2 and gRPC proxies
❏ Circuit breakers
❏ Health checks
❏ Staged rollouts with %-based traffic split
❏ Fault injection
❏ Rich metrics

15. Istio | Security Overall

16. Istio | Security

17. Istio | Reliability 99.999%, Latency and Caching

18. Istio | Mixer Adapters
https://istio.io/docs/reference/config/policy-and-telemetry
/adapters/

19. Istio | Sample
https://istio.io/docs/examples/bookinfo/

20. Istio
Diego Pacheco