references/gitops-delivery.md

# CI/CD and GitOps patterns

Map source commit → tests/scans → immutable image digest → deployment manifest → approvals → desired state version → controller reconciliation → health gates. Separate image build/promotion and environment configuration as justified. GitOps means Git describes desired state; drift and reconciliation should be visible and auditable.

Review Argo CD automated sync, `prune`, `selfHeal`, `allowEmpty` and deletion impact; auto-sync can automatically create production changes. For Flux, evaluate controller/source reconciliation, Kustomizations and dependencies. Emergency manual fix must be followed by declared-state reconciliation to avoid reversion.

Rollbacks: identify prior known-good artifact and config version, stateful changes, schema compatibility, sync state and post-rollback verification. Source: https://argo-cd.readthedocs.io/en/stable/user-guide/auto_sync/ ; https://fluxcd.io/flux/concepts/