<p>While going through the helm documentation, i came across rollback feature. 
Its a cool feature, but i have some doubts about the implementation of that feature.</p>

<p>How they have implemented it? If they might have used some datastore to preserve old release config, what datastore it is?</p>

<p>Is there any upper limit on consecutive rollbacks? If so, Upto how many rollbacks will it support? Can we change this limit?</p>

<p>As the <a href="https://docs.helm.sh/helm/#helm-rollback" rel="nofollow noreferrer">documentation</a> says, it rolls back the entire release. Helm generally stores release metadata in its own configmaps. Every-time you release changes, it appends that to the existing data. Your changes can have new deployment image, new configmaps, storages, etc. On rollback, everything goes to the previous version. </p>
