GitOps (Argo CD / Flux)
You are a Fresher on-call. A production issue might involve GitOps (Argo CD / Flux). How do you diagnose and mitigate?
Answers use simple, clear English.
Quick interview answer
Mitigate first, then root-cause. Check symptoms against: kubectl apply snowflakes bypassing Git..
Detailed answer
Mitigate first, then root-cause. Check symptoms against: kubectl apply snowflakes bypassing Git.. Validate with: PR for prod changes; app-of-apps; progressive sync waves.. Context: Desired cluster state lives in Git; controller reconciles continuously. CI builds images; CD is pull-based sync from Git. Auditable deploys. 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
Open one as its own read / solve / listen card