A transit agency’s Helm-managed addon starts failing after a bad release; ops needs the previous working revision back. Which Helm capability restores that earlier release revision?
Select an answer to reveal the explanation.
Short Explanation
Think of Helm revisions like save-points in a transit ops console—if the new build breaks the fare-gate addon, you roll back to the last good save. helm rollback puts that prior release revision back in play. Cordon, lint, or nuking kube-system do not restore a Helm revision.
Full Explanation
Helm stores release history as revisions. When a chart upgrade introduces a broken addon configuration, helm rollback returns the release to a specified earlier revision. That is distinct from node scheduling controls, chart linting, or destructive namespace deletion, none of which reverse Helm release state.