Istio: Architecture and Components
What you'll learn: How Istio's control and data planes collaborate to provide comprehensive service mesh functionality for your microservices.
What is Istio?
Istio is one of the most popular open-source service mesh implementations. It follows the architecture pattern you've learned—separating the control plane from the data plane—but implements it with specific components and features.
The Two-Plane Architecture
Data Plane: Envoy Sidecars
Istio uses Envoy proxies (which you learned about earlier) as sidecar containers deployed alongside each service instance. These Envoy sidecars intercept all network traffic to and from your services, handling:
- Traffic routing and load balancing
- Mutual TLS encryption
- Request retries and circuit breaking
- Metrics collection and distributed tracing
Think of each Envoy sidecar as a smart traffic cop stationed at every service's doorstep, enforcing policies and gathering intelligence.
Control Plane: istiod
Istio consolidates its control plane into a single binary called istiod (formerly split into Pilot, Citadel, and Galley). The istiod component manages:
- Configuration distribution: Pushes routing rules, policies, and traffic management settings to all Envoy proxies
- Service discovery: Integrates with Kubernetes or other platforms to track service instances
- Certificate management: Issues and rotates TLS certificates for mTLS between services
- Policy enforcement: Translates high-level policies into Envoy-compatible configurations
How They Work Together
You define traffic rules using Istio's Kubernetes custom resources (like VirtualService, DestinationRule). The istiod control plane watches these resources, converts them into Envoy configuration, and pushes updates to all sidecar proxies. The proxies then enforce these rules transparently—your application code remains unchanged.
Key Takeaway: Istio's architecture pairs istiod (centralized control plane) with distributed Envoy sidecars (data plane), allowing you to configure service mesh behavior once at the control plane while enforcement happens at every service boundary.