Configure a Pod Disruption Budget
Ensure a minimum number of Pods remain available during cluster maintenance and rolling updates.
Prerequisites
- The target Pods must be running.
- Note the labels of the Pods to protect in advance.
Step 1. Open the Create PDB form
Select Policy → Pod disruption budgets from the left sidebar. Click the Create pod disruption budget button in the top right.
Step 2. Enter basic information
| Field | Description | Example |
|---|---|---|
| Name | PDB name | my-app-pdb |
| Namespace | Target namespace | default |
Step 3. Configure Pod Selector
Select the Pods to protect using labels.
| Key | Value |
|---|---|
app | my-app |
Step 4. Choose a protection strategy
Select either Min Available or Max Unavailable.
| Strategy | Description | When to Use |
|---|---|---|
| Min Available | Minimum number or percentage of Pods to keep running | When minimum availability is critical |
| Max Unavailable | Maximum number or percentage of Pods that can be disrupted at once | When update speed matters |
Configuration examples
| Total Pods | Setting | Meaning |
|---|---|---|
| 3 | minAvailable: 2 | Keep at least 2 (max 1 simultaneous disruption) |
| 5 | maxUnavailable: 1 | Allow max 1 simultaneous disruption |
| 10 | minAvailable: 80% | Keep at least 80% (8 Pods) running |
WARNING
PDBs only apply to voluntary disruptions (e.g., node drains, rolling updates). They do not protect against involuntary disruptions like node failures.
Step 5. Confirm creation
Click Create. Verify the created PDB in the Pod disruption budgets list.
- Allowed Disruptions: Number of Pods that can currently be disrupted
- Current Healthy: Number of currently healthy Pods