voluntary disruption
A pod removal that someone chose, such as draining a node for maintenance, as opposed to an involuntary one like hardware failure.
In more detail
Voluntary disruptions go through the eviction API and respect PodDisruptionBudgets. Involuntary ones, such as a kernel panic or the out-of-memory killer, ignore budgets entirely. Planning maintenance around budgets keeps availability predictable.
Related terms
- PodDisruptionBudget — An object that limits how many pods of an application may be voluntarily taken down at once, such as during a node drain.
- drain — Cordoning a node and then evicting its pods through the eviction API so it can be safely maintained or removed.
- eviction — Removing a running pod from its node, either through the API during maintenance or by the kubelet when the node runs short of resources.
Taught in
- Node Affinity, Pod Affinity And Topology Spread — Kubernetes: Production-Grade Container Orchestration
- Taints, Tolerations And Disruption Budgets — Kubernetes: Production-Grade Container Orchestration
- kubeadm, High Availability And Cluster Lifecycle — Kubernetes: Production-Grade Container Orchestration
- Drain, Upgrade, Version Skew And Certificate Maintenance — Kubernetes: Production-Grade Container Orchestration