Kubernetes is often touted to be the perfect tool for deploying and managing your web application, with observability, health checks and release management all baked in. The "rolling update" functionality promises to provide seamless deployments where new versions are guaranteed to be running before the old version is terminated.

That's what I thought as well - until I discovered a small, loose thread in the perfect weave. Join me as I pull on it and share the story of how I started learning about the inner workings of Kubernetes through what seemed like a curious bug! I will also reveal how to effectively navigate around this hidden pitfall in Kubernetes.

Intermediate kubernetes knowledge