Service Mush: Debugging Istio Deployments
summary
Deploying Istio often hides specific failures: a 90/10 virtualservice split shows as 50/50 because the Service port name lacks a protocol, fixed by renaming to HTTP-backend; a quick load check with recipe (1000 requests) confirms behavior. Diagnose with istioctl proxy-config and proxy status, kube logs/stern, jq and increased Envoy log level to trace. Missing telemetry often means broken Mixer handlers so reapply mixer config. 503s during mTLS usually come from conflicting destination rules; use istioctl authn tls-check and remove the conflicting rule.
AI-written summary · about
chapters (42)
- 0:00Introduction
- 0:32The basics
- 0:43Challenges
- 1:55Automation
- 3:29Complexity
- 5:02Release Schedule
- 6:01Overview
- 6:40Architecture
- 8:15Traffic Routing
- 8:42SEO Traffic API
- 9:06Demo App
- 9:27The Problem
- 12:18Logs
- 13:03Missing subset naming field
- 15:43Istio CTL Proxy Configuration
- 16:02Istio Frontend
- 16:45Endpoints
- 17:14Routes
- 17:47Filter Command
- 18:26Allow Any
- 19:35Backend Definition
- 20:27Mesh Pods
- 23:05Traffic Example
- 23:54Mixer
- 24:21Prometheus
- 25:00Mixer Issues
- 26:29Telemetry Issues
- 27:53MTLS
- 28:27Citadel
- 29:15Policy
- 31:00Refreshing
- 31:48Weather
- 32:16Control Plane Health
- 35:05Control Plane Refresh
- 35:16grep for
- 36:10TLS check
- 37:57Delete old configuration
- 38:21Update existing configuration
- 39:14Update destination rules
- 39:54Recap
- 40:14Tools
- 41:23Questions
related talks
33mObserving and Troubleshooting your Microservices with Istio
34mIstio, We Have a Problem! Understanding and Fixing Bugs with a Service-Mesh
19mIstio, we have a problem! Understanding and fixing bugs with a service-mesh
36mIstio, we have a problem! Understanding and fixing bugs with a service-mesh
35mIstio, We Have a Problem! Understanding and Fixing Bugs with a Service Mesh
50mDeveloping Microservices with Istio
55mEmpower Your Microservices with Istio Service Mesh
52mEmpower Your Microservices with Istio Service Mesh