Maintenance

Eviction API requests pass through a PDB budget gate to selected Pods. Direct deletion, normal rolling updates and failures bypass or are not prevented by that gate. Ready does not prove application quorum.

A PodDisruptionBudget limits eviction-based disruption

A PodDisruptionBudget limits eviction-based disruption for a selected group of Pods. It can help preserve serving capacity or quorum during maintenance, but cannot guarantee either. Its protection depends on the caller using the Eviction API, the selector identifying the intended members, and Ready conditions meaning something useful for the application. ...

Three schematic backlog containers receive work: one has a small queue and open drain, one has a larger queue and open drain, and one has a blocked drain.

Vacuum keeps a growing database from bloating

In multi-version storage, deleting a row records the change without immediately freeing the space. Reclaiming that space is maintenance work, and when it is skipped the cost shows up slowly. Deleted does not mean gone An UPDATE or DELETE leaves old PostgreSQL row versions until they are no longer needed by any relevant snapshot. A long transaction can delay that point while other sessions keep changing rows. The transaction alone does not manufacture new bloat in an otherwise idle table. Reclaiming obsolete versions and making their space reusable is distinct from merely committing the delete. ...

A maintenance timer should leave its last result visible

Scheduling is only half the job; operators also need to see when the task last ran and how it ended.