After a flaky Helm upgrade of a city permitting dashboard, helm history lists several failed revisions. What should the developer do before choosing a rollback target?
Select an answer to reveal the explanation.
Short Explanation
Think of helm history like a restaurant’s ticket rail of past cooks: you look back before you rewind the kitchen. Spot a revision that was actually serving traffic, then roll to that plate—not a burnt one.
Full Explanation
Helm stores release revisions for each install or upgrade. After a failed upgrade, helm history shows which revisions succeeded or failed so you can pick a known-good target for helm rollback. Skipping history risks rolling back to another broken revision or abandoning Helm’s release tracking entirely.