Kubernetes Pod Eviction on a Pressured Node
Kubernetes pod eviction is PAINFUL 👇
But sometimes, it had to be done.
Okay.
In our story,
we have 3 happy pods on Node-1.
And Memory spikes up high on NODE-1: Now what?
“Kubernetes has a decision to make.”
“It must evict a pod.”
“Which one?”
That’s where QoS classes helps Kubernetes.
At any point, a Pod can have 1 of the following QoS classes:
1. Guaranteed
2. Burstable
3. BestEffort
When a Node is under pressure,
Pod with BestEffort QoS takes priority for eviction.
Burstable next.
Guaranteed last.
Unfortunately, Pod3 has BestEffort QoS.
So gets evicted first.
Happy endings though. Pod3 gets welcomed on Node-2 ☺️
Hope it helped. Repost if useful ♻️
If you are interested in Kubernetes & devops, checkout Mutha Nagavamsi.
P.S. Share your thoughts about QoS classes below. It helps everyone.
Thank you so much for reading this. If you found it interesting, do spread the word about it. You may also find my other content interesting, find them below.
1. Mutha Nagavamsi on Youtube. (Subscribe, it really helps)
3. Me on X.
