All 28 GitOps Principles questions
More in GitOps Principles
What tools implement GitOps besides ArgoCD? What is idempotency and why does it matter in GitOps? What is configuration drift and how does GitOps handle it? What are the benefits of GitOps over traditional deployment approaches? What belongs in Git and what should not in a GitOps setup? How are secrets managed securely in a GitOps workflow? How does GitOps improve security and compliance? How does GitOps enable auditability and compliance evidence? What is the difference between GitOps and Infrastructure as Code (IaC)? How do you handle non-Kubernetes resources in a GitOps model?
Advertisement
ArgoCD › GitOps Principles

How do you perform a rollback in a GitOps workflow?

Intermediate

Answer

The GitOps way is to revert the change in Git (revert the commit or point the app to a previous revision/tag), letting the agent reconcile the cluster back. ArgoCD also offers an app-level rollback to a previous synced revision from history, but the durable approach keeps Git as truth so the rollback is itself versioned.
# Git-first rollback
git revert <bad-commit> && git push
# or ArgoCD history rollback
argocd app rollback my-app <history-id>
Real-world example A regression is undone by reverting the offending commit; ArgoCD syncs the cluster to the known-good state within a minute.

Common follow-ups: Why prefer a Git revert over an imperative rollback? | Where is app history stored?

Sync & Health Applications GitOps Principles
All 28 GitOps Principles questions