How to purge previous RS in argo-rollouts after promotion

[evgeniy-ivlev-archie]

Hello.

When I promote a RS in Argo Rollouts, the previous one remains there with zero pods.

It's polluting a little the interface with lots of empty RS (zero pods). Is it possible to auto-remove them?'

Thanks kindly in advance for your help.

[kostis-codefresh]

I think setting revisionlimit to a lower number (or even zero) should work https://argo-rollouts.readthedocs.io/en/stable/best-practices/#reducing-operator-memory-usage

Did you try this already?

[DimitryZH]

Yes, revisionHistoryLimit is usually the main mechanism for this.

In practice, keeping it at a low value (for example 1 or 2) helps reduce ReplicaSet clutter while still preserving limited rollback history.
Something like:
spec:
revisionHistoryLimit: 1
One thing to keep in mind is the tradeoff between UI cleanliness and rollback depth. Setting it to 0 minimizes stale ReplicaSets, but also removes historical revisions very aggressively, which may reduce rollback/debugging flexibility during incident analysis.

For GitOps-style environments, a small non-zero value is often a reasonable balance.