Skip to content

Istio

Last Updated: September 11, 2026 · Istio 1.31 guidance

This overview keeps the earlier chapter URL usable. The maintained Istio documentation index and installation guide own the detailed procedures and compatibility matrix; use them for current setup.

Table of Contents

Introduction

Istio is an open-source service mesh platform for microservices applications. A service mesh is an infrastructure layer that handles service-to-service communication, allowing infrastructure-level control and observation of service communication. Application trace-context propagation, graceful shutdown and business idempotency still require application participation.

What is a Service Mesh?

A service mesh provides the following core capabilities:

  1. Traffic Management: Control traffic flow between services
  2. Security: Encryption and authentication of service-to-service communication
  3. Observability: Visibility into service-to-service communication

Key Benefits of Istio

  • Platform Independence: Works in various environments (Kubernetes, VM, etc.)
  • Transparent Integration: Many network controls can be added without changing application business logic
  • Workload mTLS: Managed identity and transport protection on enrolled mesh paths; verify enforcement and exceptions
  • Advanced Traffic Management: Routing, load balancing, fault injection, etc.
  • Detailed Metrics: Detailed metrics on service-to-service communication
  • Policy Enforcement: Access control and explicitly configured local/global rate limiting

Key Features

1. Traffic Management

Istio provides powerful traffic management capabilities:

  • Gateways: Route external traffic; distinguish Istio Gateway resources from Kubernetes Gateway API
  • VirtualService / HTTPRoute: Configure routing using the API supported by the selected data plane and controller
  • DestinationRule: Configure load balancing and connection pools
  • Traffic Splitting: Support for Canary deployments and A/B testing
  • Argo Rollouts Integration: Progressive delivery with separately configured analysis and failure handling

2. Security

Comprehensive security features:

  • mTLS: Identity authentication and encryption for enrolled workload transport
  • Authorization Policy: Fine-grained access control
  • Request Authentication: JWT validation; use AuthorizationPolicy when a JWT must be present
  • Peer Authentication: Inbound workload mTLS policy

3. Observability

Telemetry and backend integrations, configured for the selected mode:

  • Metrics: Prometheus integration
  • Distributed Tracing: Configured trace provider/backend, such as OpenTelemetry with Jaeger; applications propagate context
  • Logging: Access logs and structured logging
  • Visualization: Kiali dashboard

4. Resilience

Service resilience patterns:

  • Circuit Breaker: Connection/request-pool limits; not a guarantee against overload
  • Retry: Explicit budgets for retry-safe operations; disable ambiguous write retries
  • Timeout: Request timeout configuration
  • Outlier Detection: Exclude unhealthy instances
  • Rate Limiting: Configured local token buckets or a global rate-limit service

Architecture Overview

Istio consists of a Control Plane and a Data Plane. The following diagram shows the sidecar form, not the ambient topology.

Istiod in the control plane pushes configuration down to the Envoy sidecar proxies running alongside application containers in three data-plane pods, and those proxies establish mutual TLS connections directly with one another.

Istiod in the control plane pushes configuration down to the Envoy sidecar proxies running alongside application containers in three data-plane pods, and those proxies establish mutual TLS connections directly with one another.Open full screen ↗

Control Plane (istiod)

istiod is the central control component of Istio, providing:

  • Service Discovery: Maintains the mesh's service registry
  • Configuration Management: Watches configuration, translates it and distributes proxy settings; Kubernetes persists the API resources
  • Certificate Management: Manages workload certificate requests and rotation with the configured CA

Data Plane: Sidecar and Ambient

In sidecar mode, Envoy runs alongside each enrolled application Pod:

  • Traffic Routing: Controls traffic between services
  • Load Balancing: Distributes traffic across service instances
  • Security: mTLS encryption and authentication
  • Observability: Collects metrics, logs, and traces

Ambient uses node-level ztunnel for L4 transport and optional Envoy waypoints for supported L7 features. It does not inject an Envoy into every application Pod. Feature support, policy attachment and resource usage differ by mode; neither a fixed resource-saving percentage nor universal performance superiority follows from this topology. See Ambient Mode.

Detailed Documentation

The links below are a learning map into the maintained subtree. Its index includes additional and newly added topics.

📚 Basic Documentation

DocumentDescription
Installation GuideIstio installation and initial setup
Core ConceptsBasic concepts and terminology of Istio
ComponentsIstio architecture and components

🚦 Traffic Management

DocumentDescription
Gateway & VirtualServiceIngress/Egress Gateway configuration
RoutingVirtualService routing rules
DestinationRuleService traffic policies
Traffic SplittingCanary deployment and A/B testing
Timeout and RetryTimeout and retry policies
Load BalancingVarious load balancing strategies
Circuit BreakerCircuit breaker pattern implementation
Fault InjectionChaos engineering
Traffic MirroringTraffic mirroring and shadow testing
Session AffinitySession affinity configuration

🔐 Security

DocumentDescription
mTLSService-to-service mTLS configuration
Authorization PolicyAccess control policies
Request AuthenticationJWT-based authentication
Peer AuthenticationService-to-service authentication

📊 Observability

DocumentDescription
MetricsPrometheus metrics collection
Distributed TracingJaeger/Zipkin integration
LoggingAccess logs and structured logging
VisualizationKiali, Grafana dashboards

💪 Resilience

DocumentDescription
Outlier DetectionUnhealthy instance detection
Rate LimitingLocal and global rate limiting
Zone Aware RoutingLocality-aware routing

🚀 Advanced Topics

DocumentDescription
Ambient ModeSidecar-less service mesh
Multi-clusterMulti-cluster mesh configuration
EnvoyFilterEnvoy customization
DNS Capture and CachingDNS capture, resolution and measured cache behavior
gRPCgRPC protocol support
WebSocketWebSocket connection support
Sidecar InjectionSidecar injection mechanism
Argo RolloutsProgressive Delivery integration

✅ Best Practices

DocumentDescription
Best PracticesProduction checklist and recommendations

Quick Start

  1. Check the exact Istio/Kubernetes/EKS compatibility intersection in the installation guide. A generic “Kubernetes 1.28+” prerequisite is not sufficient for a current Istio release.
  2. Choose sidecar or ambient and follow that guide's pinned CLI/chart, isolated namespace and platform prerequisites. Do not download an unspecified latest CLI and then change into an old version directory.
  3. Use the matching-version Bookinfo procedure and gateway instructions in the maintained guide. The default profile does not automatically provide an ingress gateway Deployment, and a Gateway configuration object alone does not create every installation's required gateway/LoadBalancer.
  4. Verify the actual gateway address, Service port, route status and HTTP response. A load balancer may publish an IP or hostname; do not assume an AWS-only hostname field or a particular port name.
  5. Install/configure the chosen observability backends before using dashboard commands. Prometheus, Grafana, Kiali and tracing storage are not automatically installed by the default Istio profile.

Basic verification after completing that procedure:

bash
istioctl version
istioctl analyze -A
istioctl proxy-status

Proxy status is only one diagnostic input. Ambient enrollment and ztunnel need their own checks, and a clean analyzer result is not an end-to-end traffic test.

Learning Resources

Official Documentation

AWS and Community

Additional Resources

Quiz

To test your understanding of Istio, try the Istio Quiz.

The quiz covers the following topics:

  • Service mesh basic concepts
  • Istio architecture
  • Traffic management (Canary deployment)
  • Security (mTLS)
  • Gateway and Ingress
  • Observability tools
  • Sidecar and ambient modes
  • Rate Limiting
  • Locality routing
  • Amazon EKS integration

Next Steps: Refer to the Installation Guide to install Istio, and learn basic concepts in Core Concepts.