DevOps Daily with Fexingo · 2026-08-03 · 13 min
In this episode of DevOps Daily, Lucas and Luna dig into a surprisingly common Kubernetes failure: StatefulSets that keep rolling out old images because the controller's ordering logic interacts badly with image pull policies and rolling update strategies. Using a concrete example from a payment-processing service at a European fintech, they explain why 'Always' pull policy can mask a stale image, why the ordinal index (pod-0, pod-1...) creates a false sense of progress, and how a single misconfigured update strategy can leave pods running old code for weeks. They walk through the exact kubectl commands to verify what image each pod is actually running and how to fix the rollout without deleting the StatefulSet. Along the way, they touch on the difference between onDelete and RollingUpdate, the role of revision history, and why you should never trust 'kubectl rollout status' alone. If you've ever scratched your head wondering why your StatefulSet isn't updating, this episode gives you a mental model and a debugging path.
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