Let's talk about pod disruption in Kubernetes. Suppose you're running a bunch of happy little pods in your cluster, and then you discover that one of your nodes needs to be replaced because of a hardware issue. What do you do? Well, if you're a Kubernetes cluster, you just terminate the heck out of that sucker, running workloads be damned. State? Nobody uses state around here, what are you even talking about.
Share this post
Disruption, Eviction, Evacuation, Preemption…
Share this post
Let's talk about pod disruption in Kubernetes. Suppose you're running a bunch of happy little pods in your cluster, and then you discover that one of your nodes needs to be replaced because of a hardware issue. What do you do? Well, if you're a Kubernetes cluster, you just terminate the heck out of that sucker, running workloads be damned. State? Nobody uses state around here, what are you even talking about.