Tracing KubeVirt traffic with Istio

" summary

Explains how Istio’s sidecar proxy and service-mesh features (mTLS, retries, circuit breaking) are used to observe and route traffic, demonstrated with a canary deployment example on Kubernetes Pods. Compares networking and routing differences between regular pods and KubeVirt-managed virtual machines, describes the specific changes implemented to let Istio proxy and route traffic for containerized VMs, and shows the same canary scenario running on VMs.

AI-written summary · about

" related talks

• 32mKubeVirt + Istio: Virtual Machines on KubernetesCarlos Z Reyes, Carlos Eduardo Simon Zepeda · KCD Guadalajara 2025
• 35mIntroduction to service mesh with Istio and KialiAlissa Bonas · Riga Dev Days 2019
• 28mIstio in Action: Taking Kubernetes Traffic Control to the Next LevelAlex Parra · KCD Guadalajara 2025
• 43mService Mesh for developersAbdel Sghiouar · Voxxed Days Thessaloniki 2023
• 58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...Ben Hall · NDC Porto 2019
• 01h 06mIstio on Kubernetes: Smart Canaries, Dark Launches and ChaosBurr Sutter · Silicon Valley Code Camp 2018
• 23mRunning VM workload on Kubernetes using KubeVirtNeependra Khare · AzConf 2020
• 26mAn Introduction to Service Mesh in ActionJason Dudash · Conf42 Cloud Native 2022