In the GitOps dashboard you will also see a complete history of all past deployments as recorded in Git. You can select any of the previousversion and rollback your application to the respective version.

In the GitOps dashboard you will also see a complete history of all past deployments as recorded in Git. You can select any of the previousversions and rollback your application to the respective version.

{% include image.html

lightbox="true"

The Rollback simply informs the cluster to use a different git hash for the sync process. It doesn't affect your Git repository and ArgoCD will now show your application as out-of-sync (because the last Git commit no longer matches the status of the cluster).

This rollback behavior is best used as an emergency measure after a failed deployment where you want to bring the cluster back to a previous state in a temporary manner. If you wish to keep the current rollbackstatue as a permanent status it is best to use the standard`git reset/revert` commands and change the GitOps repository to its desired state.

This rollback behavior is best used as an emergency measure after a failed deployment where you want to bring the cluster back to a previous state in a temporary manner. If you wish to keep the current rollbackstatus as a permanent status it is best to use the standard`git reset/revert` commands and change the GitOps repository to its desired state.