How Kubernetes Finalizers Locked Our Namespace for Three Weeks
from DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations Hosted by Fexingo
In Episode 160 of DevOps Daily, Lucas and Luna drill into a deceptively simple Kubernetes footgun: object finalizers and namespace deletion. When a team at a mid-sized fintech tried to clean up a failed release, a single finalizer on a custom resource (CRD) silently held the namespace in 'Terminating' for three weeks. The episode walks through exactly how finalizers work under the hood, why the namespace didn't just vanish, how they finally traced it via kubectl and the API server logs, and the three guardrails they now enforce: auditing finalizers before deletion, using kubectl patch to remove them only when safe, and linting CRDs to block finalizers that don't self-heal. Lucas and Luna also discuss when a finalizer is worth keeping (like for cleanup jobs) versus when it becomes a footgun, and they stress-test a couple of common workarounds. No fluff, just a real ops story with concrete commands you can use today. #Kubernetes #Finalizers #Namespaces #CRD #DevOps #CloudNative #Troubleshooting #kubectl #APIServer #ClusterOps #SRE #Fintech #ProductionIssue #TechOps #CloudInfrastructure #DevOpsDaily #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.