Prev Next

Maven / GitOps Interview Questions

What is drift detection and how does a GitOps operator handle drift?

Drift is the condition where the actual state of the cluster diverges from the desired state declared in Git. Common causes: an engineer runs kubectl scale manually during an incident, a node failure causes a deployment controller to change replica counts temporarily, or a helm upgrade is run outside the GitOps workflow. Without drift detection, these deviations are invisible until something breaks.

A GitOps operator detects drift by continuously repeating the same comparison it uses for normal syncs: it fetches the current live resources from the Kubernetes API and diffs them against the rendered desired state from Git. There is no separate "drift check" mode — drift detection is simply what happens between the commit that caused the last sync and the next one.

Argo CD marks an Application as OutOfSync when it detects drift. If selfHeal: true is set in the sync policy, Argo CD re-applies the Git state immediately, reverting the manual change. If not set, the Application stays OutOfSync and shows the diff in the UI, requiring a human to click Sync.

Flux marks its Kustomization resource as not Ready when drift occurs. With the default configuration (prune: true and a polling interval), Flux will re-apply on the next interval cycle. There is no explicit "selfHeal" toggle — Flux always reconciles on its interval.

Drift tolerance is configurable: you can tell Argo CD to ignore specific fields (like status fields managed by other controllers) using ignoreDifferences in the Application spec, preventing false-positive drift alerts from controllers that write back to managed resources.

What Argo CD Application sync status indicates the live cluster state differs from the Git-declared desired state?
Which Argo CD sync policy option causes Argo CD to automatically revert manual kubectl changes?

Invest now in Acorns!!! 🚀 Join Acorns and get your $5 bonus!

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Earn passively and while sleeping

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.


Webull! Receive free stock by signing up using the link: Webull signup.

More Related questions...

What is GitOps and what core principles does it define? How does GitOps differ from traditional CI/CD pipelines? What is the 'single source of truth' principle in GitOps? What are the two GitOps deployment models: push-based vs pull-based? What is a GitOps operator and what role does it play? What is declarative infrastructure and why does GitOps require it? How does GitOps improve security and auditability compared to script-based deployments? What Git branching strategies are commonly used with GitOps? What is drift detection and how does a GitOps operator handle drift? What is the difference between GitOps and Infrastructure as Code (IaC)? What is Argo CD and how does it implement GitOps? How does Argo CD's sync process work — desired state vs live state? What are Argo CD Applications and ApplicationSets? How do you structure a GitOps repository — app-of-apps, environment folders, overlays? What is Flux CD and how does it differ from Argo CD? How does Flux's source-controller and kustomize-controller work together? How do you manage secrets in a GitOps workflow — Sealed Secrets, SOPS, External Secrets Operator? How do you handle multiple environments (dev/staging/prod) in a GitOps repo? How does image automation work in Flux for continuous delivery? What are Argo CD sync policies — automated vs manual — and sync waves? How do you roll back a deployment using GitOps? How do you integrate GitOps with a CI pipeline — separation of concerns? What is progressive delivery and how does it relate to GitOps — Argo Rollouts, Flagger? How do you handle Helm charts in a GitOps workflow? How do you use Kustomize overlays in a GitOps repository? How do you implement multi-cluster GitOps at scale? How does Argo CD handle RBAC and multi-tenancy? What are the Argo CD app-of-apps and ApplicationSet patterns and when do you use each? How do you implement GitOps for infrastructure provisioning with Crossplane and Cluster API? How do you observe and alert on GitOps sync failures in production? How do you manage database schema migrations in a GitOps workflow? How do you implement policy enforcement in a GitOps pipeline — OPA/Gatekeeper, Kyverno? What are the limitations and anti-patterns of GitOps? How do you migrate an existing deployment pipeline to GitOps? How does GitOps fit into a platform engineering strategy?
Show more question and Answers...

Testing

Comments & Discussions