GitOps (Argo CD / Flux)
What are the key trade-offs of GitOps (Argo CD / Flux)? When would you choose it vs alternatives?
Answers use simple, clear English.
Audio N/AQuick interview answer
Pros: Drift detection; easy rollback via Git revert. Cons: Secrets in Git need Sealed Secrets/ESO.
Detailed answer
Pros: Drift detection; easy rollback via Git revert. Cons: Secrets in Git need Sealed Secrets/ESO. Decision: pick when benefits outweigh operational cost. Core: Desired cluster state lives in Git; controller reconciles continuously. CI builds images; CD is pull-based sync from Git. Auditable deploys. Real-time example: Update image tag in GitOps repo → Argo CD syncs Deployment. Pros: Drift detection; easy rollback via Git revert. Cons: Secrets in Git need Sealed Secrets/ESO. Common mistakes: kubectl apply snowflakes bypassing Git. Best practices: PR for prod changes; app-of-apps; progressive sync waves. Audience level: Architect.
Full explanation
Desired cluster state lives in Git; controller reconciles continuously. CI builds images; CD is pull-based sync from Git. Auditable deploys.
Real example & use case
Update image tag in GitOps repo → Argo CD syncs Deployment.
Pros & cons
Pros: Drift detection; easy rollback via Git revert. Cons: Secrets in Git need Sealed Secrets/ESO.
Common mistakes
kubectl apply snowflakes bypassing Git.
Best practices
PR for prod changes; app-of-apps; progressive sync waves.
Follow-up questions
- How would you test GitOps (Argo CD / Flux)?
- What metrics prove GitOps (Argo CD / Flux) is healthy in prod?
- How does GitOps (Argo CD / Flux) change at 10× traffic?