Pod Disruption Budgets: Availability Assurance
65%
Use Case and Motivation
In the previous sections, we understood how to drain and cordon nodes before performing upgrades. This process helps ensure that workloads are safely evicted and rescheduled, minimizing downtime.
Imagine this scenario:
- You have 2 nodes in your cluster: NODE1 and NODE2.
- You have deployed 2 Deployments:
- Deployment A — a critical application with 5 replicas
- Deployment B — an internal tool, not critical for business continuity, with 2 replicas
- Both Deployments have the QoS class set to
Guaranteed
Cloud-Native Microservices With Kubernetes - 2nd Edition
A Comprehensive Guide to Building, Scaling, Deploying, Observing, and Managing Highly-Available Microservices in KubernetesEnroll now to unlock all content and receive all future updates for free.