Kubernetes
PodDisruptionBudget Feasibility Checker
Enter replica count and minAvailable or maxUnavailable values to determine if voluntary disruptions (node drains, updates) are possible under the configured PDB.
No data is transmitted — everything runs locallyTool
About this tool
PodDisruptionBudget Feasibility Checker
The PodDisruptionBudget Feasibility Checker computes voluntary disruption allowance from replica count and PDB configuration, flagging configurations that block all disruptions.
• Check if a PDB will block node drain during a cluster upgrade
• Verify that minAvailable allows at least one pod to be evicted for rolling updates
• Detect a PDB configured to block all disruptions (minAvailable=100%)
• Model PDB settings that allow drain while maintaining minimum availability
Affiliate disclosure
Developer-friendly cloud infrastructure. DigitalOcean provides cloud compute, networking, and managed databases with predictable pricing.
PDB configuration is a CKA exam domain — certify your k8s admin skills
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The PodDisruptionBudget Feasibility Checker computes voluntary disruption allowance from replica count and PDB configuration, flagging configurations that block all disruptions.
What affects the result most?
PodDisruptionBudget feasibility: minAvailable + maxUnavailable must be satisfiable given replica count. minAvailable: 2 with 3 replicas = only 1 pod can be disrupted — feasible. minAvailable: 100% (or replicas count) — blocks all voluntary disruptions including node drain.
How should I use the result?
Treat the tool's output as a first-pass check, not a proof of correctness. A clean pass means no issues in the patterns this tool recognizes; a failure points to a specific problem you can investigate in your source. The underlying spec is the authoritative source for edge cases.