Episode 102 of DevOps Daily dives into a lesser-known risk with Kubernetes Vertical Pod Autoscaler (VPA): its ability to cause cascading instability in production workloads. Lucas and Luna walk through a real-world case where VPA's recommender triggered simultaneous resource resizing across multiple microservices, leading to pod evictions, request timeouts, and a multi-hour incident at a mid-sized SaaS company. They explain VPA's resource recommendation algorithm, why its default mode forces pod restarts, and how a simple configuration change — setting updateMode to 'Off' — turned VPA from a destabilizing force into a safe guidance tool. The episode also covers how to pair VPA with Horizontal Pod Autoscaler (HPA) without conflict, key metrics to monitor (pod restart rate, P99 latency), and a practical workflow: run VPA in recommendation-only mode, review changes during off-peak hours, apply manually. Perfect for teams already using HPA and wondering if VPA is worth the complexity — spoiler: it is, but only with guardrails.