pod-disruption-budget.md (849B)
1 +++ 2 title = 'Pod disruption budget' 3 +++ 4 # Pod disruption budget 5 Pods may be disrupted because of events: 6 - involuntary: hardware failure, destruction of node's VM, eviction of pod because node runs out of resources 7 - voluntary: deleting Deployment, update of Deployment causing a restart, deletion of pod, draining of ndoe 8 9 To mitigate involuntary disruption: 10 - ensure pod requests the resources it needs 11 - replicate application if you need higher availability 12 - spread apps across racks (using anti-affinity) or across zones 13 14 To deal with voluntary disruption: 15 - app owners can create PodDisruptionBudget to limit number of Pods of replicates app that are down simultaneously 16 - makes sense when app owner and cluster admin are different people/roles/vendors 17 - reduction in number of pods during involuntary disruption will count against the budget