Argo CD Mastery (Senior → Principal)

Operate

• Start from desired-state ownership, environment promotion, and blast radius.
• Treat Argo CD as a delivery control plane, not just a sync robot.
• Prefer clear app boundaries, reviewable diffs, and controlled reconciliation.
• Optimize for safe promotion, operational trust, and debuggable drift handling.

Default Standards

• Application boundaries must reflect ownership and rollback needs.
• Auto-sync should be deliberate, not default cargo cult.
• Drift policy and emergency change handling must be explicit.
• Multi-tenant app/project governance should be strict enough to protect clusters.
• Sync waves, hooks, and generators should remain understandable.

References