PodDisruptionBudget YAML Generator

A PodDisruptionBudget (PDB) protects the availability of an application during voluntary disruptions such as node drains and cluster upgrades. The PodDisruptionBudget YAML Generator writes that manifest from a form so you do not have to recall the policy/v1 schema.

You set the PDB name and namespace, then choose how many pods must stay available - either minAvailable or maxUnavailable, each given as an integer or a percentage. Finally you add a label selector (matchLabels) that picks the pods the budget covers. The resulting YAML is valid policy/v1.

The name is validated as an RFC 1123 label, the selector needs at least one label, and at least one of minAvailable or maxUnavailable is required. Problems are reported in a clear panel. Everything runs locally and nothing is uploaded.

• minAvailable - integer or percentage that must stay up.
• maxUnavailable - integer or percentage that may be down.
• Selector - matchLabels (key=value, comma separated).
• policy/v1 - correct schema.
• Validation - RFC 1123 name, required selector and threshold.
• Copy / Download / Print - get pdb.yaml wherever you need it.

1. Name the PDB. Type a valid RFC 1123 name.
2. Set minAvailable or maxUnavailable. e.g. 2 or 50%.
3. Add selector labels. e.g. app=web.
4. Watch the preview and export.

Example 1 - min available. minAvailable 2 for a three-replica service.

Example 2 - percentage. minAvailable 50% keeps half up.

Example 3 - max unavailable. maxUnavailable 1 allows one down.

Example 4 - app label. selector app=web.

Example 5 - tier. selector tier=frontend.

• Correct schema - valid policy/v1 PodDisruptionBudget.
• Flexible thresholds - integer or percentage, min or max.
• Validated - names and required fields checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.