GitOps (Argo CD / Flux)
Give a real production-style example of using GitOps (Argo CD / Flux). Walk through the scenario end-to-end.
Answers use simple, clear English.
Audio N/AQuick interview answer
Scenario: Update image tag in GitOps repo → Argo CD syncs Deployment. Implementation notes: PR for prod changes; app-of-apps; progressive sync waves.
Detailed answer
Scenario: Update image tag in GitOps repo → Argo CD syncs Deployment. Implementation notes: PR for prod changes; app-of-apps; progressive sync waves. 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: Fresher.
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?