LinkedIn runs on bare metal, so they care a LOT about not moving things around. You literally see every single failure that happens when a pod gets moved.
Discussion
Loading...
Discussion
LinkedIn runs on bare metal, so they care a LOT about not moving things around. You literally see every single failure that happens when a pod gets moved.
There are extremely few knobs in Kubernetes to manage evictions, and most of them are "on/off" knobs, you don't get any fine-grained policies or configs around disruption.
(AND half the core kubernetes controllers ignore the controls that exist in the first place, 😡 )
First way to evict a pod is the pod delete API. Kubernetes didn't terminate your pod, you terminated your pod!
It doesn't do PDB checks!!!! Deployment controller uses this, so rollouts don't even check this!
Second way to evict a pod is the pod eviction API, which does respect PDBs.
This is the last time you will hear about the eviction API. Nobody uses it. Which is a real &$*%ing shame because everything should.
Can you write a webhook for the eviction API?
🤔
We're going to come back to this.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled