Hello and welcome to this Deep Dive Thursday! I’m Lauro Müller, and I’m super happy to have you here with me 😄 Let’s spend a few minutes to sharpen our skills and learn something new and relevant for running production systems, shall we? Today we will explore in details why Deployments fall short for production releases, and how Argo Rollouts provide a considerably more robust setup for safe releases. Ready to get started? Let’s go!
Kubernetes Deployments are good at one thing: replacing Pods without taking the application down all at once.
That is a big win when compared to creating Pods or ReplicaSets directly, yes, but when it comes to production releases, it has many shortcomings.
A Pod can become Ready, join the Service, and still break things the moment real traffic hits it.
And that’s a big problem. Although Kubernetes sees a healthy Pod, your actual users may see failed requests, weird latency spikes, or a feature that looked fine in testing but falls apart in production. Not the best UX, right?
Why Deployments Are Not Enough
This begs the question: why are Deployments not enough?