How Kubernetes Service Mesh Istio Sidecars Cache Memory Until OOM
from DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations Hosted by Fexingo
In this episode of DevOps Daily with Fexingo, Lucas and Luna dive into a common but often overlooked problem in Istio service meshes: sidecar Envoy proxies that cache DNS and configuration data until they exhaust pod memory and trigger OOM kills. They break down why the default 2 GiB memory limit for Envoy in Istio 1.20 is not a safety net but a ticking time bomb, especially when sidecars cache full service entries for large clusters. Using the example of a 500-service cluster running Istio 1.22, they explain how Envoy's memory usage scales linearly with the number of endpoints and how a single misconfigured DestinationRule can cause the sidecar to allocate heap for every possible route. They also cover mitigation strategies: setting fine-grained memory limits per workload, enabling Envoy's memory limit agent, and using Wasm filters to reduce runtime memory consumption. By the end, you'll understand why 'just give it more memory' is the wrong answer and how to profile sidecar memory with Envoy's admin endpoint and /stats before it's too late. #Kubernetes #Istio #ServiceMesh #Envoy #OOMKill #SidecarMemory #CNCF #CloudNative #DevOps #SRE #PodResources #MemoryLeak #IstioSidecar #K8sPerformance #FexingoBusiness #BusinessPodcast #Technology #DevOpsDaily Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.