I'm using Argo Rollouts and ArgoCD.
When I try to rollback a rollout in argo rollouts, it is immediately reverted by ArgoCD as I've enabled auto-sync.
How should I tackle this problem?
If there was a method by which ArgoCD would know it's a rollback and would write-back to git.
ArgoCD doesn't support writing commits back to git. If you have auto-sync enabled in your ArgoCD application then the best way to perform a rollback is to revert your commit in git. Once the commit is reverted (which technically creates a new commit containing the revert), ArgoCD will automatically sync the latest commit into your k8s cluster. Which effectively rolls back the change by performing a new change.
