GitOps (Argo CD / Flux)
Go deep on GitOps (Argo CD / Flux): edge cases, scalability limits, and how you'd evolve the solution over 2 years.
Answers use simple, clear English.
Audio N/AQuick interview answer
Desired cluster state lives in Git; controller reconciles continuously. CI builds images; CD is pull-based sync from Git.
Detailed answer
Desired cluster state lives in Git; controller reconciles continuously. CI builds images; CD is pull-based sync from Git. Auditable deploys. Scale limits often appear in: Secrets in Git need Sealed Secrets/ESO.. Evolution levers: PR for prod changes; app-of-apps; progressive sync waves.. Anchor example: Update image tag in GitOps repo → Argo CD syncs Deployment. 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: Junior.
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
Only answered follow-ups are shown — click to open with full answers