DevOps Daily with Fexingo · 2026-08-27 · 10 min
In this episode, Lucas and Luna dig into a frustrating Kubernetes mystery: a service mesh that quietly added latency to every request without triggering any alarms. They walk through a real-world incident where mTLS handshakes and sidecar proxies doubled p99 response times, yet dashboards showed everything green. The conversation covers how to spot the hidden cost of service meshes, why metrics like CPU and memory miss it, and the concrete debugging steps that finally exposed the culprit: an Envoy proxy with an oversized connection pool and a misconfigured retry policy. If you run Istio, Linkerd, or any sidecar-based mesh, this episode gives you a checklist to avoid the same silent performance trap. They also touch on when a mesh is worth the overhead and when it might be simpler to step back to plain Kubernetes networking. #Kubernetes #ServiceMesh #Istio #Linkerd #Envoy #SidecarProxy #mTLS #Latency #DevOps #SRE #Observability #Performance #Troubleshooting #TechPodcast #FexingoBusiness #BusinessPodcast #CloudNative #K8s Keep every episode free: buymeacoffee.com/fexingo
How Kubernetes Namespace Quotas Trigger Unexpected Failures58 / 100Why Your Kubernetes Cost Reports Are Lying To YouHow Kubernetes Node Pools Can Cost You More Than You ThinkHow Kubernetes Pod Overhead Changes Node Capacity CalculationsHow Kubernetes Pod Security Admission Blocks Risky Workloads