Skip to content
Back to skills

Pdb

ASecurity

PodDisruptionBudgets — the pdb-blocks-drain lint and render warning for a PDB that can never allow a disruption, and the pruning of stale forge-labelled PDBs when a workload drops to one replica.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 13, 2026
developmentgonode

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add reliant-labs/forge --skill pdb --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pdb?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pdb
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/reliant-labs-pdb/badge)](https://www.skillsdirectory.com/skills/reliant-labs-pdb)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: deploy/pdb
description: PodDisruptionBudgets — the pdb-blocks-drain lint and render warning for a PDB that can never allow a disruption, and the pruning of stale forge-labelled PDBs when a workload drops to one replica.
---

# PodDisruptionBudgets

forge renders a PDB (`maxUnavailable: 1`) only above one replica. Two guards keep PDBs from blocking node drains:

- **A PDB that can never allow a disruption is flagged** — `minAvailable >= replicas`, `maxUnavailable: 0`, or `minAvailable: 100%`, on forge-rendered PDBs and your own `forge.Manifests` alike. `forge lint` reports it as `pdb-blocks-drain` (warning) and `forge env deploy` / `up` print a render-time warning naming the object. Fix: `maxUnavailable: 1`, or delete the PDB while the workload runs one replica.
- **Stale PDBs are pruned.** Dropping a workload to one replica stops rendering its PDB. Under Flux, `prune: true` removes it (PDBs are never prune-guarded). On the direct-apply path, `forge env deploy` deletes forge-labelled (`managed-by=forge`) PDBs of any workload in the render whose PDB the render no longer carries — PDBs only, and never one forge did not label. A PDB that belongs to no workload in the render at all (a replaced component's `openbao-pdb`, two budgets over the same pods) is caught by the owned-object prune instead: any PDB stamped `forge.dev/owner` that the render no longer carries goes once the rollout is healthy (`deploy/plan`).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.