Which configuration should you use in your ArgoCD Application YAML?
hard📝 Best Practice Q15 of 15
Kubernetes - Advanced Deployment Patterns
You want to ensure that ArgoCD only deploys changes to your Kubernetes cluster after manual approval, but still track changes in Git automatically. Which configuration should you use in your ArgoCD Application YAML?
ASet <code>syncPolicy: automated: {}</code> to enable auto deploy
BOmit <code>syncPolicy</code> and use manual sync to approve changes
CSet <code>syncPolicy: automated: null</code> to disable auto deploy
DSet <code>syncPolicy: automated: { prune: true, selfHeal: true }</code> for auto deploy with cleanup
Step-by-Step Solution
Solution:
Step 1: Understand manual approval need
To require manual approval before deployment, auto sync must be disabled.
Step 2: Configure syncPolicy accordingly
Omitting syncPolicy disables auto sync, so ArgoCD tracks Git but waits for manual sync.
Final Answer:
Omit syncPolicy and use manual sync to approve changes -> Option B
Quick Check:
No syncPolicy = manual approval required [OK]
Quick Trick:No syncPolicy means manual sync only [OK]
Common Mistakes:
Using automated sync disables manual approval
Setting automated with prune/selfHeal still auto deploys
Setting automated: null is invalid syntax
Master "Advanced Deployment Patterns" in Kubernetes
9 interactive learning modes - each teaches the same concept differently
