Old ReplicaSets for a library catalog Deployment keep accumulating and clutter etcd, but the team still wants some undo depth. Which field tunes how many old ReplicaSets are retained?
Select an answer to reveal the explanation.
Short Explanation
How many old blueprints you keep in the cabinet is a storage vs undo tradeoff. revisionHistoryLimit caps retained ReplicaSets—high enough to roll back, low enough to avoid clutter.
Full Explanation
Deployment .spec.revisionHistoryLimit controls how many old ReplicaSets are kept for rollback. Lower values reclaim objects sooner; higher values preserve deeper undo history via kubectl rollout undo. completed/successfulJobsHistoryLimit belong to Job/CronJob history, and backoffLimit is a Job retry field—not Deployment revision retention.